Re: blowing right by breakpoints
Re: blowing right by breakpoints
- Subject: Re: blowing right by breakpoints
- From: Rudi Sherry <email@hidden>
- Date: Tue, 20 Dec 2005 14:19:20 -0800
Also, there is a known bug with breakpoints in C++ constructors.
There are two constructors (and two destructors) created for each
class (having to do with subclassing), and when you set the
breakpoint in the constructor, you are setting it in only one ... if
that's not the one that's called, you're SOL.
On Dec 20, 2005, at 1:27 PM, Chris Friesen wrote:
The next time your program is stopped at a breakpoint open the
debugger console and enter 'info b' to print the breakpoint state.
This will show us if the breakpoints you aren't stopping at are
<PENDING> or are set somewhere weird.
-ChrisF
On Dec 20, 2005, at 12:39 PM, Bob Stuller wrote:
Greetings!
The program stops at the first breakpoint in a C++ method and then
ignores all the breakpoints in the C code until the flow of
execution returns to the next breakpoint back in the C++. What
I've tried:
Compile all code in C++.
Compile by file type.
Turn off 'load symbols lazily'.
Any idea what's going on?
TIA!
Peace,
Bob
Let us not look back in anger, nor forward in fear, but around in
awareness.
- James Thurber
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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