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: Shawn Erickson <email@hidden>
- Date: Wed, 5 Aug 2009 12:01:50 -0700
On Tue, Aug 4, 2009 at 7:30 PM, n179911<email@hidden> wrote:
> On Tue, Aug 4, 2009 at 7:20 PM, Jason Molenda<email@hidden> wrote:
>> This backtrace was made without debug info (a dSYM) or the tool that
>> produced the backtrace did not try to provide file+line information from the
>> debug info.
>>
>
> 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?
Are you selecting the "Debug" or "Release" configuration? Does the
project even have those configurations?
Please go review the Xcode documentation for topics related to build
configurations and build settings.
<http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeBuildSystem/000-Introduction/Introduction.html>
>> 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?
Any directory... none of the listed command care about the current
working directory (at least in the example he posted). Just "man
c++filt" to understand better what that command line tool does.
-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