Re: EXC_BREAKPOINT crash when debugging with Xcode 3.2
Re: EXC_BREAKPOINT crash when debugging with Xcode 3.2
- Subject: Re: EXC_BREAKPOINT crash when debugging with Xcode 3.2
- From: Jim Ingham <email@hidden>
- Date: Wed, 7 Oct 2009 17:35:13 -0700
First step for any Xcode debugging issue is to turn on the Xcode-gdb
log (in the Debugging Tab of the Xcode preferences.) Then when
something bad happens, save the log, file a bug describing what
happened and include the log.
In the case where enabling/disabling breakpoints causes your app to
quit, it may be that the debugger is getting some kind of error and
exiting (which would cause your app to quit too.) If so we'll see
that in the log. It's also possible that the debugger is crashing.
If that happened, you should see a crash log in ~/Library/Logs with a
name like: gdb-i386-apple-darwin**** where the ***'s will be a date
and some other junk (the format of these names has changed over time,
but they always have the process name in them...) These logs don't
get cleaned up (except by you if you delete them) so there may be some
old ones there. Those aren't so useful to us, since we don't know
what gdb version they go to. But next time you get this "exited with
result 1" error, look to see if there's a new one there. If so
include that with the log in a Radar.
Thanks,
Jim
On Oct 7, 2009, at 5:27 PM, Brad Oliver wrote:
I have a fairly unusual yet very annoying problem.
Sometimes when debugging my app, I'll be stopped in the Xcode
debugger investigating some code. Not frequently, but often enough,
the debugger will stop responding to my attempts to twiddle
disclosure triangles to see variables. If I wait long enough,
eventually I get a system crash dialog noting an exception of type
EXC_BREAKPOINT. Needless to say, my debugging session ends. ;-)
A separate, but possibly related, issue is that sometimes when
enabling or disabling breakpoints, my app will spontaneously quit,
and Xcode will note that it exited with the result 1. No crash
dialog results in this case. So now I'm leery of enabling/disabling
breakpoints while debugging.
More background info: I'm debugging a 32-bit Intel-only Mac app that
is heavily C++ based. I've seen this happen on both a gimpy iMac
Core Duo 1.8 GHz and a early 2008 quad-core Mac Pro, both with
10.6.1/Xcode 3.2/gcc 4.0. There are roughly 1100 .cpp source files
in this project.
This is not reproducible with any regularity. What can I do to help
track this down?
For the moment I have enough hair that I can afford to keep pulling
it out, but it's becoming a limited resource. ;-)
--
Brad Oliver
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