• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to pin point where is the exception from a Backtrace in XCode
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: n179911 <email@hidden>
  • Date: Tue, 4 Aug 2009 19:30:30 -0700

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?

> 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?

Thank you for your help again.


> But without a dSYM made for your binary, you won't be able to get a
> file+line.  If you're familiar with i386 assembly you can often figure it
> out if you disassemble the function and read closely.
>
> If you have a dSYM for this application, load it into gdb and try
>
> (gdb) info line *0x0066cf55
>
> J
>
> On Aug 4, 2009, at 7:13 PM, n179911 wrote:
>
>> Hi,
>>
>> In my Xcode console, I get the following backtrace during debug: Can
>> you please tell me how can I find out which line of which file causing
>> the fault?
>>
>> Thank you.
>>
>>
>> Backtrace:
>>        0   Chromium                            0x0066cf55
>> _Z18PR_ParseTimeStringPKciPx + 50879
>>        1   Chromium                            0x00691e88
>> _Z18PR_ParseTimeStringPKciPx + 202226
>>        2   Chromium                            0x006b7c02
>> _Z18PR_ParseTimeStringPKciPx + 357228
>>        3   Chromium                            0x000bf9ae start + 774718
>>        4   Chromium                            0x005e076f
>> _ZNK2v86HandleINS_6NumberEEdeEv + 110403
>>        5   Chromium                            0x005e0818
>> _ZNK2v86HandleINS_6NumberEEdeEv + 110572
>>        6   Chromium                            0x005f7510
>> _ZNK2v86HandleINS_6NumberEEdeEv + 204004
>>        7   Chromium                            0x00dc524b
>> _ZN2v86LockerC2Ev + 2192009
>>        8   Chromium                            0x0121f98f
>> _ZNK2v86HandleINS_5ValueEEeqIS1_EEbNS0_IT_EE + 473537
>>        9   Chromium                            0x0121fb17
>> _ZNK2v86HandleINS_5ValueEEeqIS1_EEbNS0_IT_EE + 473929
>>        10  Chromium                            0x0121fbe3
>> _ZNK2v86HandleINS_5ValueEEeqIS1_EEbNS0_IT_EE + 474133
>>        11  Chromium                            0x01200f8f
>> _ZNK2v86HandleINS_5ValueEEeqIS1_EEbNS0_IT_EE + 348097
>>        12  Chromium                            0x012476a8
>> _ZN2v810PersistentINS_5ValueEE7DisposeEv + 62598
>>        13  Chromium                            0x01244850
>> _ZN2v810PersistentINS_5ValueEE7DisposeEv + 50734
>>        14  Chromium                            0x0186c46b
>> _ZN2v86HandleINS_5ValueEEC1INS_6NumberEEENS0_IT_EE + 820077
>>        15  Chromium                            0x00de1984
>> _ZN2v86LockerC2Ev + 2308546
>>        16  Chromium                            0x000aaf4f start + 690143
>>        17  Chromium                            0x000ace6e start + 698110
>>        18  Chromium                            0x000af6b2 start + 708418
>>        19  Chromium                            0x000aa08d start + 686365
>>        20  Chromium                            0x000ab7a9 start + 692281
>>        21  Chromium                            0x0002fcb1 start + 185665
>>        22  Chromium                            0x00c0ed75
>> _ZN2v86LockerC2Ev + 396723
>>        23  Chromium                            0x00c100ef
>> _ZN2v86LockerC2Ev + 401709
>>        24  Chromium                            0x00c1012b
>> _ZN2v86LockerC2Ev + 401769
>>        25  Chromium                            0x00694c95
>> _Z18PR_ParseTimeStringPKciPx + 214015
>>        26  Chromium                            0x00695059
>> _Z18PR_ParseTimeStringPKciPx + 214979
>>        27  Chromium                            0x006954db
>> _Z18PR_ParseTimeStringPKciPx + 216133
>>        28  Chromium                            0x0069eb91
>> _Z18PR_ParseTimeStringPKciPx + 254715
>>        29  Chromium                            0x00695e8d
>> _Z18PR_ParseTimeStringPKciPx + 218615
>>        30  Chromium                            0x00695ea9
>> _Z18PR_ParseTimeStringPKciPx + 218643
>>        31  Chromium                            0x00695f34
>> _Z18PR_ParseTimeStringPKciPx + 218782
>>        32  Chromium                            0x0061e83e
>> _ZNK2v86HandleINS_6NumberEEdeEv + 364562
>>        33  Chromium                            0x00003e83 start + 5907
>>        34  Chromium                            0x000028e7 start + 375
>>        35  Chromium                            0x000027a6 start + 54
>> _______________________________________________
>> 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

  • Follow-Ups:
    • Re: How to pin point where is the exception from a Backtrace in XCode
      • From: Shawn Erickson <email@hidden>
    • Re: How to pin point where is the exception from a Backtrace in Xcode
      • From: Jason Molenda <email@hidden>
References: 
 >How to pin point where is the exception from a Backtrace in XCode (From: n179911 <email@hidden>)
 >Re: How to pin point where is the exception from a Backtrace in XCode (From: Jason Molenda <email@hidden>)

  • Prev by Date: Re: How to pin point where is the exception from a Backtrace in XCode
  • Next by Date: Re: How to pin point where is the exception from a Backtrace in Xcode
  • Previous by thread: Re: How to pin point where is the exception from a Backtrace in XCode
  • Next by thread: Re: How to pin point where is the exception from a Backtrace in Xcode
  • Index(es):
    • Date
    • Thread