Re: gdb: "No line number information available for address...." :(
Re: gdb: "No line number information available for address...." :(
- Subject: Re: gdb: "No line number information available for address...." :(
- From: Jason Molenda <email@hidden>
- Date: Tue, 28 Jul 2009 15:03:40 -0700
On Jul 28, 2009, at 2:44 PM, Jerry Krinock wrote:
Here are the relevant settings in my .app Target in Xcode which
generates the dSYM file:
DEBUG_INFORMATION_FORMAT = dwarf-with-dsym
GCC_GENERATE_DEBUGGING_SYMBOLS = YES
GCC_DEBUGGING_SYMBOLS = default
I just tried to do another build. Here's the relevant part of the
Build Transcript:
Building target “Bookdog” of project “Bookdog” with configuration
“Release”
Checking Dependencies
GenerateDSYMFile /Users/jk/Documents/Programming/Builds/Release/
Bookdog.app.dSYM /Users/jk/Documents/Programming/Builds/Release/
Bookdog.app/Contents/MacOS/Bookdog
cd /Users/jk/Documents/Programming/Projects/Bookdog
/Developer/usr/bin/dsymutil /Users/jk/Documents/Programming/
Builds/Release/Bookdog.app/Contents/MacOS/Bookdog -o /Users/jk/
Documents/Programming/Builds/Release/Bookdog.app.dSYM
warning: no debug symbols in executable (-arch i386)
warning: no debug symbols in executable (-arch ppc)
Either the app was built without debug information or the app was
stripped before the GenerateDSYMFile. By the time dsymutil ran on
Bookdog, the debug symbols were not present. You can run dwarfdump on
one of your .o files like we did with the dSYM earlier -- does it have
any DWARF debug info in it? If not, then the files are not being
built with debug info. Look for the Strip phase in your build log -
is it happening before the GenerateDSYMFile?
So, it's warning me. Why might GenerateDSYMFile put "no debug
symbols in executable"? And if indeed this is true, what's in those
3,251,947 bytes that it generated? Looks like lots of information
to me!
The best way to introspect this is to use otool, e.g. "otool -arch
i386 -hlv Bookdog.app.dSYM/Contents/Resources/DWARF/Bookdog" you can
skip down to the LC_SEGMENT load command for the __DWARF segment and
see how much space all of the DWARF debug info is using.
As Jonas suggested in his email, it's worthwhile to look at the ppc
side of your dSYM as well to see what's in there - I'm specifying -
arch i386 in all of these examples so you don't get confused by the
presence of ppc debug info when you need i386 debug info.
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