🚀 go-pugleaf

In article <6224@ucsbcsl.ucsb.edu> doug@foxtrot.ccmrc.ucsb.edu (Douglas  
Scott) writes:
> Can someone who has used the malloc debugging features of the compiler  
(via
> malloc_debug() and malloc_error()) please tell me the specific meaning  
of the
> following error messages:
> 
> node overflow
> node underflow
> free node trashed
> 

I'm assuming you are linking with MallocDebug since that is where these  
error strings exist.

  agog> strings /usr/lib/libMallocDebug.a | grep node
  node underflow: %p
  node overflow: %p
  free node trashed: %p

The malloc debug library places guard data at the beginning and end of  
malloced data, so I'm guessing that the overflow and underflows are  
corruptions of this guard data. Free node trashed means that you wrote  
over freed data.
In theory if you run /NextDeveloper/Apps/MallocDebug, the trashed data  
should be marked at the top when you look at malloced memory.

My personal favorite is to not use libMallocDebug.a but to pepper my code  
with a define that when enabled calls NXMallocCheck().

It will slow down your code, but nicely isolate where the memory trash is  
occurring. 


	-greg.	


-- 
Greg Cockroft                       greg@agog.com    
Agog, Inc.                          (517) 627-2186   fax 2673
13780 North River Highway
Grand Ledge, MI  48837