• 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
gdb: "No line number information available for address...." :(
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gdb: "No line number information available for address...." :(


  • Subject: gdb: "No line number information available for address...." :(
  • From: Jerry Krinock <email@hidden>
  • Date: Tue, 28 Jul 2009 12:38:26 -0700

Today I received a crash report from a user. The good news is that I don't get these very often, but this means that due to lack of experience I'm never sure if I'm doing something wrong when my attempt to symbolize the crash report fails, as it just did.

My script which I use to ship my application produces a .dSYM file for the app and all of its dependent frameworks. From the crash report [1], I see that the binary which provoked the crash is x86 and has identifier 'com.sheepsystems.Bookdog'. From the "Binary Images" section [2], I see that the uuid of this binary is d6b29b64312aa4f1532d8309df9642da. I open the .dSYM package which my script had produced for this build and in its Info.plist, and verify that the dSYM_UUID.i386 property is the same, D6B29B64-312A- A4F1-532D-8309DF9642DA. Yippee.

So I unzip my zipped archive of Bookdog 5.3.3, move it into the same directory with this .dSYM and the other frameworks' .dSYM files, cd to this directory, fire up gdb, and ask for the names of the three com.sheepsystems.Bookdog symbols in the call stack of the crash.

Unfortunately, in all three cases, I get the dreaded "No line number information available for address...."

Jerrys-Mac-Mini:Bookdog_5.3.3 jk$ gdb
GNU gdb 6.3.50-20050815 (Apple version gdb-962) (Sat Jul 26 08:14:40 UTC 2008)
Copyright 2004 Free Software Foundation, Inc. <snip> legal notice </ snip>
This GDB was configured as "i386-apple-darwin".
(gdb) set sharedlibrary preload-libraries no
(gdb) file Bookdog.app/Contents/MacOS/Bookdog
Reading symbols from /Users/jk/Documents/Programming/Builds/Shipped/ Bookdog_5.3.3/Bookdog.app/Contents/MacOS/Bookdog...Reading symbols from /Users/jk/Documents/Programming/Builds/Shipped/Bookdog_5.3.3/ Bookdog.app.dSYM/Contents/Resources/DWARF/Bookdog...done.
done.
(gdb) info line *0x0006eadd
No line number information available for address 0x6eadd
(gdb) info line *0x0005faa8
No line number information available for address 0x5faa8
(gdb) info line *0x0006f5dc
No line number information available for address 0x6f5dc


I then try to get info the for call at the bottom of the stack, which is presumably my main(). But it can't even find main()!...

(gdb) info line *0x00002249
No line number information available for address 0x2249
(gdb)

Am I doing something wrong, or is gdb crash symbolizing a hit-and-miss operation that sometimes just doesn't work. If the latter, is there anything I can do to improve my chances?

Sincerely,

Jerry Krinock


[1]

Process:         Bookdog [11689]
Path:            /Applications/Bookdog.app/Contents/MacOS/Bookdog
Identifier:      com.sheepsystems.Bookdog
Version:         5.3.3 (5.3.3)
Code Type:       X86 (Native)
Parent Process:  launchd [118]

Interval Since Last Report:          231955 sec
Crashes Since Last Report:           4
Per-App Interval Since Last Report:  5179 sec
Per-App Crashes Since Last Report:   2

Date/Time:       2009-07-28 10:56:02.314 -0700
OS Version:      Mac OS X 10.5.7 (9J61)
Report Version:  6
Anonymous UUID:  8454207D-0BD3-42C9-A5DE-1B98E0ED1366

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
Crashed Thread:  0

Thread 0 Crashed:
0 com.apple.CoreFoundation 0x9690b975 CFArrayCreate + 37
1 com.apple.CoreFoundation 0x969e7dd8 -[__NSPlaceholderArray initWithObjects:count:] + 424
2 com.apple.CoreFoundation 0x969f458f - [__NSFastEnumerationEnumerator initWithObject:] + 287
3 com.apple.CoreFoundation 0x969e8753 -[NSArray objectEnumerator] + 67
4 com.sheepsystems.Bookdog 0x0006eadd 0x1000 + 449245
5 com.sheepsystems.Bookdog 0x0006f5dc 0x1000 + 452060
6 com.sheepsystems.Bookdog 0x0005faa8 0x1000 + 387752
7 com.apple.AppKit 0x91efc4cb -[NSApplication sendAction:to:from:] + 112
8 com.apple.AppKit 0x91efc408 -[NSControl sendAction:to:] + 108
9 com.apple.AppKit 0x91efc28e -[NSCell _sendActionFrom:] + 169
10 com.apple.AppKit 0x91efb8e7 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 1827
11 com.apple.AppKit 0x91efb13a -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 541
12 com.apple.AppKit 0x91efa9f4 -[NSControl mouseDown:] + 888
13 com.apple.AppKit 0x91ef9133 -[NSWindow sendEvent:] + 5381
14 com.apple.AppKit 0x91ec5cd9 -[NSApplication sendEvent:] + 2941
15 com.apple.AppKit 0x91e2362f -[NSApplication run] + 847
16 com.apple.AppKit 0x91df0834 NSApplicationMain + 574
17 com.sheepsystems.Bookdog 0x00002322 0x1000 + 4898
18 com.sheepsystems.Bookdog 0x00002249 0x1000 + 4681




[2]

Binary Images:
0x1000 - 0xa3ffb +com.sheepsystems.Bookdog 5.3.3 (5.3.3) <d6b29b64312aa4f1532d8309df9642da> /Applications/Bookdog.app/Contents/ MacOS/Bookdog
0xd1000 - 0xdcffe +com.sheepsystems.BmStuff ??? (1.0) <fbd3b8b0be76baa5c590e2bd721e2764> /Applications/Bookdog.app/Contents/ Frameworks/BmStuff.framework/Versions/A/BmStuff
0xe6000 - 0xf6fff +com.sheepsystems.SSApp ??? (1.0) <10cf9eff84b8b9db6dd429393dfba145> /Applications/Bookdog.app/Contents/ Frameworks/SSApp.framework/Versions/A/SSApp
0x103000 - 0x10ffff +net.brockerhoff.RBSplitView.Framework 1.1.4 (1.1.4) <ee038cb6802b8553c344a1aab04cc0a5> /Applications/Bookdog.app/ Contents/Frameworks/RBSplitView.framework/Versions/A/RBSplitView
0x119000 - 0x12bfff +org.andymatuschak.Sparkle 1.5 Beta (bzr) (1.5) <23c0facf9930b31ad95aaf7274965501> /Applications/Bookdog.app/ Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
0x13a000 - 0x146ffb +com.sheepsystems.SSAlert ??? (1.0) <94f202acfbeaac0e4518fcc384471f0a> /Applications/Bookdog.app/Contents/ Frameworks/SSAlert.framework/Versions/A/SSAlert
0x150000 - 0x151ffc +com.sheepsystems.SSYLocalize ??? (1.0) <e8905d660bfa6815cc37831a116e36f1> /Applications/Bookdog.app/Contents/ Frameworks/SSYLocalize.framework/Versions/A/SSYLocalize
0x164000 - 0x164fff +com.yazsoft.SDEnhancer ??? (1.0) <aaf8bec2f8678a549c9cd50fc1a04ce4> /Library/InputManagers/ SpeedDownload Enhancer/SpeedDownloadEnhancer.bundle/Contents/MacOS/ SpeedDownloadEnhancer
0x17e000 - 0x189fff +com.rogueamoeba.audio_hijack_server.hermes 2.1.1 (2.1.1) <194ae68f3731862fb1702d10e446aa16> /usr/local/hermes/ modules/Instant Hijack Server.hermesmodule/Contents/MacOS/Instant Hijack Server
0x1fa000 - 0x1fafff +com.ksuther.chax.loader ??? (2.2.2) <376f51a842f4c8c35f7429da3e82e3a1> /Library/InputManagers/Chax/ Chax.bundle/Contents/MacOS/Chax
<snip>.....




_______________________________________________
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: gdb: "No line number information available for address...." :(
      • From: Jason Molenda <email@hidden>
  • Prev by Date: Re: C++ exception breakpoint failure
  • Next by Date: dtrace: failed to compile script trace.d: line 22: probe description pid14677::objc_msgSend:return does not match any probes
  • Previous by thread: Link Issue
  • Next by thread: Re: gdb: "No line number information available for address...." :(
  • Index(es):
    • Date
    • Thread