Le jeudi 25 avril 2002, à 12:42 , Robert Covington a écrit :

> What are the main culprits to check for/track down regarding a Macsbug
> visit to Bowels of the Memory Manager error?

extreme memory corruption [and perhaps also, too much chili sauce].

look for handles that no longer exist, overstepping memory,
dereferenced handles, dangling pointers, the usual suspects...

try using zone ranger, this might help point out somewhere
just before things go wrong [remember that with the esc key
you can at least view the screen of your mac from macsbug
before rebooting].

you could also look at staz's paper on debugging
<http://www.stazsoftware.com/futurebasic/tn13.php>

i also used to turn heap scrambling on in macsbug [hs], it's a toggle,
first time you type that then return its on, then second time it's off.
as this juggles the memory around a lot, it shakes down bad code sooner.

hth,
:-j