Xref: utzoo comp.sys.mac.programmer:23318 comp.sys.mac.system:4050 comp.sys.mac.misc:10543
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!gsbacd.uchicago.edu!gft_robert
From: gft_robert@gsbacd.uchicago.edu (opcode ranger)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac.system,comp.sys.mac.misc
Subject: Virtual screws up Macsbug?? (was Re: MacsBug 6.2b1 sees ALL...)
Message-ID: <1991Apr4.145959.1@gsbacd.uchicago.edu>
Date: 4 Apr 91 20:59:59 GMT
References: <1991Apr3.195724.1@gsbacd.uchicago.edu>
Sender: news@midway.uchicago.edu (News Administrator)
Lines: 27

In article <1991Apr3.195724.1@gsbacd.uchicago.edu>, I wrote
> -- 
> 
> I was working on an app in MPW C and then in THINK C and whenever I checked
> (hc) the heap in MacsBug I kept getting "zone bad".  Fair enough, but
> I started getting "zone bad" in THINK itself, even after a reboot.  Then
> I checked, and even after a reboot, any other app besides the Finder
> gives me "zone bad" on a heap check, even if it's the first (after Finder)
> launched.

Well, thanks to the help of a net reader I was able to figure out that Virtual
(2.0.2) was causing (spurious?) readings of 'zone pointer is bad' in MacsBug
6.2b1.

Now for the important question: is Virtual actually screwing things up? Or is
MacsBug returning bogus information?  If the latter, is there a version that
won't do this?  (The person who helped me said that he'd experienced problems
also with MacsBug 6.1 and Virtual).

Robert

-- 
============================================================================
= gft_robert@gsbacd.uchicago.edu * generic disclaimer: * "It's more fun to =
=            		         * all my opinions are *  compute"         =
=                                * mine                *  -Kraftwerk       =
============================================================================