Re: "Stop on C++ throw"
Re: "Stop on C++ throw"
- Subject: Re: "Stop on C++ throw"
- From: Tim Conkling <email@hidden>
- Date: Tue, 15 Mar 2005 14:12:27 -0500
When I manually set the catchpoint with the method you describe below,
it works fine. However, when the "Stop on C++ throw" menu option is
enabled, gdb prints this out to the console:
"Cannot insert catchpoint 2; disabling it.
Error accessing memory address 0x48ff8: Input/output error."
(this is printed as the program is starting up).
Anyone know why this could be?
Also, is it possible for me to have catchpoints/watchpoints/etc
automatically entered into gdb whenever I debug my program with xcode?
Thanks,
Tim
On Mar 14, 2005, at 2:55 PM, Chris Friesen wrote:
Try gdb from the command line to isolate the issue. Break on 'main',
'run', then 'catch throw' when you stop at main, then 'info b', then
'continue' and see if the debugger stops when your C++ program throws.
-Chris
On Mar 13, 2005, at 9:21 PM, Tim Conkling wrote:
Hello list,
Turning on the "Stop on C++ throw" option in the Xcode Debug menu
doesn't work for me. With this item enabled, I would expect that
Xcode would break into the debugger when an exception was thrown in
my app while it was being debugged, but this isn't the case.
Anyone have an idea about what could be going on?
Thanks,
Tim
_______________________________________________
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