• 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: interpreting crashlog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: interpreting crashlog


  • Subject: Re: interpreting crashlog
  • From: Shawn Erickson <email@hidden>
  • Date: Wed, 27 Sep 2006 08:51:42 -0700


On Sep 27, 2006, at 7:29 AM, Perry Winkel wrote:

yep, its the line number where the function definition starts
what i was hoping for was that the line number would tell me where in
the funcrion the crash appears, but it just leads me to the first line of
the definition


i thinnk the +404 is the offset for the crashing instruction...but at what is the instruction itself, what line?

Normally the <filename>:<number> is the line in the code that is related to the point of the crash but you may have a symbol issue, the stack frame may be a little messed up, or the optimizer has moved things around causing symbol problems (DWARF seems to be the better symbol format to use).


Anyway review the following tech-note to understand how to work with crash logs...

<http://developer.apple.com/technotes/tn2004/tn2123.html>

It you have a copy of your application around with symbols then I would use GDB to statically load that application (gdb MyApplication.app). Then use things like info line *<address from 3rd column> and disassemble at particular addresses, etc.

Also for C++ you likely want to look at using c++filt and in GDB enable demangling...

QuadG5:/usr/lib shawnce$ gdb
GNU gdb 6.3.50-20050815 (Apple version gdb-563) (Wed Jul 19 05:17:43 GMT 2006)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "powerpc-apple-darwin".
(gdb) set print asm-demangle on
(gdb) set print demangle on
(gdb)


Finally look over this helpful tech-note to learn various useful debugging tips...

<http://developer.apple.com/technotes/tn2004/tn2124.html>

-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


References: 
 >interpreting crashlog (From: email@hidden)
 >Re: interpreting crashlog (From: Eric Albert <email@hidden>)
 >Re: interpreting crashlog (From: Perry Winkel <email@hidden>)

  • Prev by Date: Re: Keyboard shortcut for "Next Page" in All-in-One Layout
  • Next by Date: Re: Re: Best approach for customized project templates?
  • Previous by thread: Re: interpreting crashlog
  • Next by thread: Keyboard shortcut for "Next Page" in All-in-One Layout
  • Index(es):
    • Date
    • Thread