Re: How can I break into debugger?
Re: How can I break into debugger?
- Subject: Re: How can I break into debugger?
- From: Mark Bessey <email@hidden>
- Date: Fri, 9 Sep 2005 16:25:11 -0700
On Sep 9, 2005, at 12:26 PM, Yves Poissant wrote:
What is the function call or instruction that I should use to break
into the debugger from inside the code execution (like on an Intel
CPU, the assembly instruction "int 3")?
Is there some sort of assert function available in OSX? Where the
passed instruction result is tested and breaks into the debugger if
it fails?
Also is there any available memory management library that will
guard from spills and leaks and would generate such a break when
something odd happens with a memory bloc?
Take a look at the last few options in Xcode's Debug menu....
"Enable Guard Malloc" - enables the Guard Malloc library, which
can detect buffer overwrites, leaks, and double-frees.
"Stop on C++ catch" - stops in the debugger whenever a C++
exception is caught.
"Stop on C++ throw" - stops in the debugger whenever a C++
exception is thrown.
"Stop on Debugger()/DebugStr()" - As you might expect, these cause
the program to stop in the debugger when you call either Debugger()
or DebugStr(). Those two functions are provided by the CoreServices
framework.
There's a section on "Xcode and Mac OS X Debugging" in the Xcode
User's Guide which explains how to use some of these features...
-Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden