[Zimwy]

Hi,
Apparently, if your program is running inside of a debugger under Windows, the debugger especially looks out for the assembly call "Interrupt 3" which diverts control to the debugger, breaks, and then lets the program continue.

Is there any such call for OS X? I need to implement a debugBreak macro that lets the program continue running. I'm sortof at a loss as to how to do this.

Thanks so much for your help,
gabe

[hayesk]

What do you mean by "breaks, and continues"? Do you want to make it continue, or have it continue on its own? If it goes on its own, then what good is the debug information - it's stale as soon as the program continues.

If you mean, have it stop, you look at the info, and tell it to go again when you are ready, then yes, pretty much every Mac debugger can do this. They're called breakpoints, not Interrupt 3.

[Zimwy]

Originally posted by hayesk:
If you mean, have it stop, you look at the info, and tell it to go again when you are ready, then yes, pretty much every Mac debugger can do this. They're called breakpoints, not Interrupt 3.

Yes, I do mean this. Unfortunately it's not quite that simple. I have to write my own break point. I was hoping that someone here would know the specific command that a break point introduces to the debugger to make it listen up.

gabe

[larkost]

You are looking for the program in question to call out a breakpoint (at runtime) for the debugger? I don't know that it has this feature, but if you really want a good answer to this question, then you need to go to the right place: the MacOSX-dev list over at omnigroup. That is where the real experts on this sort of thing hang out.