🚀 go-pugleaf

In article <1992Aug18.143135.6259@cc.tut.fi> 
  mn87504@cs.tut.fi (Naatula Mika) writes:

>I wonder if this is a familiar bug to someone.

*All* bugs are familiar to me.  Solutions are harder.

>The problem is:
>Sometimes my program causes a segmentation fault. If I drive it with
>CVP I can find out (from calls sequence) that the error was caused by
>malloc. To be exact, malloc calls an internal(?) function named
>_searchseg() that fails. Any ideas what this function might be?

I had this problem before on another machine.  It turned out what
I was doing was malloc'ing space that was too small, overrunning it
and causing malloc to have a hissy fit.  I know you said you have
checked your code, but I would look for a line like

	fred = (grumble *) malloc(sizeof(grumble *));

which should be

	fred = (grumble *) malloc (sizeof(grumble));

Typedefs could compllicate this search.  Good luck.

C Frog