• 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: Making .dSYM fails
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Making .dSYM fails

  • Subject: Re: Making .dSYM fails
  • From: Michael Rawdon <email@hidden>
  • Date: Mon, 30 Apr 2007 18:05:42 -0700
Hi David -

On Apr 28, 2007, at 10:07 PM, David Dunham wrote:

I'm having trouble getting .dSYM files for one of my projects:


    cd /Users/david/GameHouse/cgames/Match3

    /usr/bin/dsymutil -o /Users/david/GameHouse/cgames/Match3/build/Release/RainforestCascade.app.dSYM /Users/david/GameHouse/cgames/Match3/build/Release/RainforestCascade.app/Contents/MacOS/RainforestCascade

ERROR: No debug map or DWARF data was found to link.

ERROR: No debug map or DWARF data was found to link.

ERROR: No debug map or DWARF data was found to link.


This is a C++ app. Debug-related custom settings:


DEBUG_INFORMATION_FORMAT = dwarf-with-dsym

ZERO_LINK = NO

DEAD_CODE_STRIPPING = YES

GCC_GENERATE_DEBUGGING_SYMBOLS = YES

GCC_DEBUGGING_SYMBOLS = full

GCC_ENABLE_SYMBOL_SEPARATION = NO

GCC_OPTIMIZATION_LEVEL = s


MACOSX_DEPLOYMENT_TARGET_ppc = 10.2

SDKROOT_ppc = /Developer/SDKs/MacOSX10.2.8.sdk


I turned off DEAD_CODE_STRIPPING and still get the same error. Looked in both Target and Project.


How mysterious.

A copy of the full build transcript for that target might be more illuminating.  Absent that, however (sorry, I'm a little punchy at the end of the day today, and my grammar is becoming byzantine), I have a few guesses as to what's happening:

1) You're building for one or more architectures with GCC-3.3 or earlier.  (DWARF is only supported when using GCC-4.0.  If you need to build with an earlier compiler, you should probably use Stabs across the board - i.e., for all architectures - as your debug format.  I'm not sure if there's a better way to alleviate this scenario.)  Since you're building for 10.2, my guess is that this might be it.

2) You're linking your binary in such a way that none of its components contain any DWARF data.  For instance, your binary links together a few different static libraries and/or object files - and nothing else - and all of the sources have already been stripped before they're used by your target.

3) You're building a truly trivial app which contains no symbols, so the compiler wasn't able to generate any DWARF information.  (This seems unlikely, though. :-)

-- 
Michael Rawdon

email@hidden
Xcode Developer

Apple Inc., Cupertino CA



 

 _______________________________________________
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: Making .dSYM fails
      • From: David Dunham <email@hidden>
References: 
 >Making .dSYM fails (From: David Dunham <email@hidden>)

  • Prev by Date: Re: LIBRARY_SEARCH_PATHS_QUOTED and HEADER_SEARCH_PATHS_QUOTED
  • Next by Date: Re: Making .dSYM fails
  • Previous by thread: Re: Making .dSYM fails
  • Next by thread: Re: Making .dSYM fails
  • Index(es):
    • Date
    • Thread