Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!das
From: das@Apple.COM (David Shayer)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacsBug ignoring breakpoints
Message-ID: <45335@apple.Apple.COM>
Date: 3 Oct 90 03:34:56 GMT
References: <1990Sep28.171459.3335@mdivax1.uucp> <24762@dartvax.Dartmouth.EDU>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 28

In article <24762@dartvax.Dartmouth.EDU> llama@eleazar.dartmouth.edu (Joe Francis) writes:
>Brian Gix writes:
>>Can anyone tell me the proper way to set breakpoints using MacsBug?
>>I have been trying to use it to debug a project I'm doing, and
>>although I know the points in the code & suppose to be breaking
>>on are being called, the breakpoint seems to have no effect.
>
>Perhaps some development environments do this for their own source level 
>debuggers.
>
>Does anyone know what happens to the exception vectors under multifinder
>if one program "Chains" another?  Does the child inherit the parents
>exception vectors?  Or does multifinder stuff in some set of "golden"
>vectors?

The _Chain trap is not supported.  Call it - it'll crash.

I have not had any problems setting breakpoints using Macsbug in
programs I'm debugging with Think C, Think Pascal, and SADE.  

If you break into Macsbug when you hit a _Debugger trap which you poke
into your code, you should break when you hit a Macsbug breakpoint.
Setting breakpoints is easy.  Just type BR ADDR.  If someone overwrites
the breakpoint, Macsbug will tell you next time you drop into Macsbug.
To see what breakpoints you have set, type BRD.  Be sure to clear your
breakpoints when you're done, type BRC.

David