Re: Xcode Goes Into Debugger Without Breakpoint or Error
Re: Xcode Goes Into Debugger Without Breakpoint or Error
- Subject: Re: Xcode Goes Into Debugger Without Breakpoint or Error
- From: Chris Espinosa <email@hidden>
- Date: Thu, 15 Jan 2009 10:38:15 -0800
On Jan 15, 2009, at 9:16 AM, Keary Suska wrote:
On Jan 14, 2009, at 7:45 PM, Jim Ingham wrote:
There should be more information in the Xcode-gdb log, which you
can turn on in the Debugger Pane of the Xcode Preferences. If you
want to chase this down further, please turn on this logging, run a
session that mysteriously stops like this, and then grab the log
and file a Radar including the log and a description of how you are
running your program.
It looks like this is the relevant message:
<- 208*stopped,time=
{wallclock
=
"13.34395
",user
=
"0.63998
",system
=
"0.35733
",start="1232038718.821371",end="1232038732.165319"},reason="signal-
received",signal-name="SIGTRAP",signal-meaning="Trace/breakpoint
trap",thread-id="1"
Does this mean that it thinks it hit a breakpoint? I can submit the
whole project in a bug report, but it requires a PostgreSQL database
(network connected) with a specific schema and data set. Please
advise.
The low-level routine __NSI0 in NSInvocation switches off of the
argument information. If the information is inconsistent or
corrupted, the default case in the switch statement executes a HALT.
That's what you're hitting; you are not providing the correct
arguments to NSInvocation.
Chris
_______________________________________________
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