Path: utzoo!attcan!uunet!wuarchive!ukma!rutgers!cunixf.cc.columbia.edu!shenkin
From: shenkin@cunixf.cc.columbia.edu (Peter S. Shenkin)
Newsgroups: comp.sys.sgi
Subject: Re: problem with malloc
Message-ID: <1990Oct26.145216.17446@cunixf.cc.columbia.edu>
Date: 26 Oct 90 14:52:16 GMT
References: <9010252231.AA23626@snowhite.cis.uoguelph.ca>
Organization: Columbia University
Lines: 17

In article <9010252231.AA23626@snowhite.cis.uoguelph.ca> mike@SNOWHITE.CIS.UOGUELPH.CA writes:
>    I probably won't be the first or the last to say this, but you've probably
>got a loose pointer on your deck somewhere.  If you write into memory that you
.....
>quite some time ago in program terms.  To help you out with this, SGI provides
>a really neat option for memory debugging called 'mallopt'.  If you look at

See also the public-domain debugging malloc routines that are available from
the comp.sources.unix archives.  After you use one of these things (or mallopt),
and debug your code, you go back to using the system malloc routine, since
these range-checking guys are inefficient.

	-P.
************************f*u*cn*rd*ths*u*cn*gt*a*gd*jb**************************
Peter S. Shenkin, Department of Chemistry, Barnard College, New York, NY  10027
(212)854-1418  shenkin@cunixc.cc.columbia.edu(Internet)  shenkin@cunixc(Bitnet)
***"In scenic New York... where the third world is only a subway ride away."***