Re: GenerateDSYMFile Invalid DWARF error
Re: GenerateDSYMFile Invalid DWARF error
- Subject: Re: GenerateDSYMFile Invalid DWARF error
- From: James Walker <email@hidden>
- Date: Tue, 22 Jun 2010 18:08:38 -0700
On 6/22/2010 5:53 PM, Jason Molenda wrote:
On Jun 22, 2010, at 5:41 PM, James Walker wrote:
On 6/22/2010 4:52 PM, Jason Molenda wrote:
Which compiler did you both use?
The easiest way to check is to inspect the .o file dsymutil is getting an error on with the "dwarfdump" command line tool. In the first few lines you'll see a line like
AT_producer( "GNU C 4.2.1 (Apple Inc. build nnnn)" )
I think this is an unknown problem.
patrick machielse said he was using GCC 4.0, and so am I. (dwarfdump says "GNU Objective-C++ 4.0.1 (Apple Inc. build 5494)".)
Thanks. Yeah, I saw that Patrick said he was using 4.0 but it's always good to check what the file was actually built with ... sometimes those sneaky compilers and do things behind our backs :)
Now I'm trying to remember WHY I'm using GCC 4.0. I think it's because compiling PPC code with GCC 4.2 produces code with the ppc7400 architecture. I guess I should check whether that's still true with this version of Xcode.
FWIW, here's the part of the dwarf dump that it seems to be complaining about:
0x000009a5: TAG_enumeration_type [24] *
AT_name( "float_round_style" )
AT_byte_size( 0x04 )
AT_decl_file( "/Xcode3.2.3/SDKs/MacOSX10.5.sdk/usr/include/c++/4.0.0/limits" )
AT_decl_line( 156 )
AT_byte_size( 0x04 )
AT_decl_file( "/Xcode3.2.3/SDKs/MacOSX10.5.sdk/usr/include/c++/4.0.0/limits" )
AT_decl_line( 156 )
AT_sibling( {0x000009ff} )
Yep, there's the problem. We added some validation checks to dsymutil in Xcode 3.2.3 to catch a problematic bit of debug information generation from the newer compilers and it looks like our testing did not catch the fact that gcc-4.0 was also emitting similarly bad debug information.
If you can use gcc-4.2, that's the best solution, as you guessed. Please file a bug report over at http://bugreport.apple.com/ - if it's possible, including the compilation line for this source file and the source code definition of your float_round_style enum may be enough for us to reproduce the exact debug info in isolation.
Sigh. Apparently I can't use GCC 4.2, since my product is supposed to
run on any Mac that can run Tiger or better. And I need to be able to
save dSyms for each build, so that I'll be able to decode crash logs
from users. So I guess it's back to Xcode 3.2.1 for me.
I'll try to distill a bug report on it. Note that it's not MY
float_round_style enum, it's in the standard <limits> header.
--
James W. Walker, Innoventive Software LLC
<http://www.frameforge3d.com/>
_______________________________________________
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