Path: utzoo!news-server.csri.toronto.edu!rutgers!mcnc!gatech!udel!wuarchive!cs.utexas.edu!solo.csci.unt.edu!ponder.csci.unt.edu!doug
From: doug@ponder.csci.unt.edu (Douglas A. Scott)
Newsgroups: comp.sys.next
Subject: malloc() problems under 2.0
Message-ID: <1991Mar4.025906.24602@solo.csci.unt.edu>
Date: 4 Mar 91 02:59:06 GMT
Sender: usenet@solo.csci.unt.edu (Usenet News)
Distribution: usa
Organization: University of North Texas, Denton
Lines: 20

I just finished recompiling the source for a large piece of software to be
sure that it would work properly under 2.0.  It is pure C code, no OOP stuff.
When I try to run it I get:

Smashed zone. Header size invalid
Malloc corrupted entering malloc

Now, this program ran under 1.0a, on Suns, Vaxen, etc., with no problems...
so what's the deal?  Is this really some coding problem that has *just*
been revealed to me for the first time by cc 2.0 on the cube? :-o
The program does do a lot of on-the-fly malloc'ing of space, but I have
been very diligent in keeping it legal.  Any ideas?  BTW, it exits sig 6
after that, and gdb doesnt catch it before it quits.

Thanks for any advice!

-- 
___________________________________________________________________________
Douglas Scott
zardoz!doug%woof.columbia.edu