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: Jason Molenda <email@hidden>
- Date: Tue, 4 Aug 2009 19:35:25 -0700
On Aug 4, 2009, at 7:30 PM, n179911 wrote:
Thank you for your detailed explanation first of all. I am not sure
why the backtrace was made without debug info. It is chrome Xcodde
project, so I go to 'Build and Debug'. The build is successful. Please
tell me to build with debug info?
That should build with debug information.
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.
You can demangle the names of your functions from the command line
like this
-
$ echo _Z18PR_ParseTimeStringPKciPx | c++filt -n
Can you please tell em which directory I should go to execute this
command?
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.
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