gft_robert@gsbacd.uchicago.edu (opcode ranger) (04/05/91)
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 = ============================================================================
anders@verity.com (Anders Wallgren) (04/05/91)
In article <1991Apr4.145959.1@gsbacd.uchicago.edu>, gft_robert@gsbacd (opcode ranger) writes: >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). > I've experienced problems with both MacsBug 6.1,6.2b1-3, and 6.2 Final when using Virtual or Maxima. I do not know if the problem is in MacsBug or the Connectix products. MacsBug 6.2 Final seems a little more stable wrt. to one problem that I was having - I would break into macsbug, but when I hit g/es/rs, etc. my mac would freeze and I would have to do a cold boot. Of course, 6.2 Final is buggier than the betas in some other areas, like stack crawl, so I guess you can't win them all. anders