Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!rutgers!mailrus!purdue!decwrl!labrea!csli!gandalf
From: gandalf@csli.STANFORD.EDU (Juergen Wagner)
Newsgroups: comp.sources.wanted
Subject: Re: source for SUNs malloc wanted
Keywords: malloc.c
Message-ID: <5414@csli.STANFORD.EDU>
Date: 9 Sep 88 19:40:15 GMT
References: <2111@hou2d.UUCP>
Reply-To: gandalf@csli.stanford.edu (Juergen Wagner)
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 12

[Sorry for posting this but I don't seem to be able to send mail to this host]

Before you're blaming malloc.c have a look at your program. The kind of 
error you are describing looks pretty much like some mangled/overwritten
pointers. If you are overwriting the housekeeping information malloc needs,
it is no longer able to do its job. I have a version of malloc that checks
its tables every time you call it, and when something's wrong it tells you!

Let me know if that's what you need.

-- 
Juergen "Gandalf" Wagner,		   gandalf@csli.stanford.edu
Center for the Study of Language and Information (CSLI), Stanford CA