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: "Shawn Erickson" <email@hidden>
- Date: Fri, 2 Mar 2007 13:17:01 -0800
On 3/2/07, Jason Molenda <email@hidden> wrote:
> 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.
We are hitting this issue as well...
We have shipped product to customers saving the dSYM file generated
from the product just before we stripped it. Anyway to repair the dSYM
files since that at the moment is the only things we maintained of the
unstripped product.
The interesting thing is this used to work just fine (used dSYM files
all the time to resymbolize crash logs reported by customers) but
something in the last product we built and shipped resulted in the
dSYM not working for the Intel build (PowerPC build seems to work).
-Shawn
_______________________________________________
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