Re: Small memory bug in gimpact

On Tue, Nov 20, 2007 at 05:15:40PM -0800, Jon Watte (ODE) wrote:
> That is the whole point. The only reason that code is there is to break 
> into the debugger when malloc() returns NULL. Which it does either when 
> you have corrupted the heap (most likely), or when you're trying to run 
> a model larger than your system can handle (less likely).

Aye, my heap was a smouldering carcass at the time [Go me!].

Thanks for all the replies,
Gary (-;