Re: How to pin point where is the exception from a Backtrace in Xcode
Re: How to pin point where is the exception from a Backtrace in Xcode
- Subject: Re: How to pin point where is the exception from a Backtrace in Xcode
- From: Jeremy Pereira <email@hidden>
- Date: Wed, 5 Aug 2009 11:36:24 +0100
On 5 Aug 2009, at 03:35, Jason Molenda wrote:
Can you cause your app to crash? If so, run it under the debugger.
In Xcode shift-command-Y should launch it under the debugger. Xcode
should show you the line where your application is crashing.
alt-command-y on my Xcode installation. shift-command-y just opens the
debugger window without running the app.
c++filt is in /usr/bin so your standard path should pick this up.
If you're not familiar with using Terminal, I would focus on using
Xcode to reproduce and debug your application's crash.
monica:~ jeremyp$ echo _Z18PR_ParseTimeStringPKciPx | c++filt -n
PR_ParseTimeString(char const*, int, long long*)
J
_______________________________________________
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
_______________________________________________
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