Re: How to debug stripped binary that has hanged
Re: How to debug stripped binary that has hanged
- Subject: Re: How to debug stripped binary that has hanged
- From: Jeff Johnson <email@hidden>
- Date: Thu, 8 May 2008 16:40:30 -0500
On May 8, 2008, at 4:02 PM, Mattias Arrelid wrote:
Hi,
I have a delicate problem; one of our users have some problems with
an application of ours - the application hangs at a certain
operation, and attaching to the process with Xcode confirms that
the main thread is waiting for a semaphore (sem_wait probably).
Now, the binary is stripped, so it doesn't contain any of our
method names - only addresses to those functions in the stripped
binary.
We do have a non-stripped version of the application that I would
like to match the above mentioned addresses against. So far, we've
used dSymbolizer to debug crashes reports from our users, and it
has worked out just fine. But... in this case, we do not have a
crash report, but rather a hang report (you do get a such if you
force quit the stalled application).
Is there _any_ easy way to match such a report through a non-
stripped binary, just as with crash reports?
Regards
Mattias
Mattias,
One way would be to use "dwarfdump --lookup=". See <http://
developer.apple.com/documentation/Darwin/Reference/ManPages/man1/
dwarfdump.1.html>. Apparently, you can only look up one address at a
time, so it's not super-easy, but it's certainly better than nothing.
-Jeff
_______________________________________________
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