Re: How to get routine names in crash logs ?
Re: How to get routine names in crash logs ?
- Subject: Re: How to get routine names in crash logs ?
- From: "Timothy J. Wood" <email@hidden>
- Date: Tue, 21 Jun 2005 08:49:55 -0700
On Jun 21, 2005, at 8:04 AM, Hugh Sontag wrote:
But crash logs (at least on Tiger, 10.4.1) don't have symbols in
them. The crash log looks like this:
Thread 4 Crashed:
0 <<00000000>> 0xffff8acc __memcpy + 812 (cpu_capabilities.h:
189)
1 bsimpd 0x00022580 0x1000 + 136576
2 bsimpd 0x00024cb8 0x1000 + 146616
3 ...ple.CoreServices.CarbonCore 0x90b387d0
PrivateMPEntryPoint + 76
4 libSystem.B.dylib 0x9002c3d4 _pthread_body + 96
The first step would be to check your build log and verify that
symbols are getting emitted into your .o files, intermediate
libraries and final executable. You can look at the symbols in your
images with 'nm'; it's man page lists a huge number of options, but
you can probably just do:
nm object-file | grep SymbolThatShouldBeThere
(Beware of C++ name mangling :)
Also, is this code in a framework or in your application? dyld
was significantly changed (read: rewritten) and programs that
interface with it needed updating to deal with this. In particular,
the compatibility API in dyld for vm_slide of images was very busted
(I've got a couple Radars on this). So, if this is a framework, you
should try setting a base address on the framework. If this is a
bundle, you will need a fixed crash catcher. If this is a normal
executable, this isn't the problem and you should this bit :)
-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