Good point. I used this in debugging a non-DX piece of code. Greg
"David L. Thompson" <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 03/03/2000 10:18:49 AM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: [email protected] cc: Subject: Re: [opendx-dev] [PATCH] netcdf problem The problem with trying to use this in the core part of the exec is that malloc is overridden so that it is never used. DX uses its own version when it comes to memory allocation. It also doesn't catch things like the problem we just had where something was writing outside of its memory bounds (due to the fact that the app has a ton of memory allocated with something other than malloc). David >Its no purify, but if you set an environment variable MALLOC_CHECK_ to 1, >you get a warning at bad alloc/free calls and some overruns, and set to 2 >it gives you an abort - easy to debug. Found this recently looking at the >malloc man page. > >Greg > >Peter Daniel Kirchner <[EMAIL PROTECTED]>@opendx.watson.ibm.com on >03/02/2000 06:14:59 PM > >Please respond to [email protected] > >Sent by: [EMAIL PROTECTED] > > >To: [email protected] >cc: >Subject: Re: [opendx-dev] [PATCH] netcdf problem > -- ............................................................................. David L. Thompson The University of Montana mailto:[EMAIL PROTECTED] Computer Science Department http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812 Work Phone : (406)257-8530
