Re: can't debug, "exited with status (11)"
Re: can't debug, "exited with status (11)"
- Subject: Re: can't debug, "exited with status (11)"
- From: Jason Molenda <email@hidden>
- Date: Fri, 2 Mar 2007 13:05:17 -0800
On Mar 2, 2007, at 12:56 PM, James Walker wrote:
Jason Molenda wrote:
On Mar 2, 2007, at 12:21 PM, James Walker wrote:
Jason Molenda wrote:
Open the Debugger Console window and see if something about the
problem is displayed there. It often is.
All it says is: "The debugger has exited due to signal 11
(SIGSEGV)."
Hm, the debugger crashed? There should be a crash log in ~/Library/
Logs/CrashReporter in that case.
So there is. Here's the stack trace...
Command: gdb-i386-apple-darwin
Path: /usr/libexec/gdb/gdb-i386-apple-darwin
Parent: Xcode [208]
Version: ??? (???)
PID: 2446
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x06a3889c
Thread 0 Crashed:
0 gdb-i386-apple-darwin 0x000f99bf dwarf_decode_lines + 1611
1 gdb-i386-apple-darwin 0x000fbbfe dwarf2_build_psymtabs + 3475
2 gdb-i386-apple-darwin 0x00166ded macho_symfile_read + 287
Hm, that looks like a bug from the way dsymutil creates dSYM files
that we fixed recently. The fix will be in the next release. Try
debugging without a dSYM file, if possible (the debug info is in
the .o files; the executable/dylib has references to those .o files)
or use stabs to work around it for now.
Jason
_______________________________________________
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