Path: utzoo!news-server.csri.toronto.edu!rutgers!uwm.edu!src.honeywell.com!msi.umn.edu!noc.MR.NET!gacvx2.gac.edu!gacvx2.gac.edu!scott From: scott@erick.gac.edu (Scott Hess) Newsgroups: comp.sys.next Subject: Re: malloc() problems under 2.0 Message-ID: Date: 5 Mar 91 00:42:10 GMT References: <1991Mar4.025906.24602@solo.csci.unt.edu> <17176@sdcc6.ucsd.edu> Distribution: usa Organization: Gustavus Adolphus College Lines: 31 Nntp-Posting-Host: 138.236.10.8 In-reply-to: cpenrose@sdcc13.ucsd.edu's message of 4 Mar 91 18:54:36 GMTLines: 31 In article <17176@sdcc6.ucsd.edu> cpenrose@sdcc13.ucsd.edu (Christopher Penrose) writes: In article <1991Mar4.025906.24602@solo.csci.unt.edu> doug@ponder.csci.unt.edu (Douglas A. Scott) writes: >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 by non-related code. I have been recommended to use the new zone allocation classes; however, I have not had time to experiment with them yet. Research and application of these new (albeit NeXT specific) memory management classes may be worthwhile. Unfortunately, using the zone-specific stuff won't cure the problems, as the regular malloc is (I believe) implemented in terms of the zone memory allocation. I, too, had some stuff which broke under certain pre-release versions of 2.0, but worked fine under 1.0. I've also got some stuff which sort of works - it runs just fine, with nary a core file in sight, but the mallocation stuff claims stoutly that other stuff is being trashed. I'm not sure what to think . . . Later, -- scott hess scott@gac.edu Independent NeXT Developer GAC Undergrad "Tried anarchy, once. Found it had too many constraints . . ." "I smoke the nose Lucifer . . . Bannana, banna."