• 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: Nothing (reliably) helpful from atos + dSYM
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Nothing (reliably) helpful from atos + dSYM


  • Subject: Re: Nothing (reliably) helpful from atos + dSYM
  • From: Rick Altherr <email@hidden>
  • Date: Thu, 20 Nov 2008 10:51:47 -0800


On Nov 20, 2008, at 10:23 AM, Nathan Vander Wilt wrote:

I recently sent out a release of an upcoming product to some alpha testers, who found a few crashers. They sent me the crashlogs and since I had generated dSYM info for the build, I gave atos a shot.

From the directory where I had both Mercatalog.app and Mercatalog.app.dSYM, I tried:
/Developer/user/bin/atos -arch x86_64 -o Mercatalog.app/Contents/ MacOS/Mercatalog 0x0000000100020ff4
but all I got back was the almost-useless:
0x0000000100020ff4 (in Mercatalog)


I used dwarfdump --uuid to compare the UUIDs between the .dSYM and the app executable and they matched.
I also tried using:
dwarfdump Mercatalog.app.dSYM --arch=x86_64 --lookup= 0x0000000100020ff4
but that didn't find anything either, although maybe I'm using that wrong (It outputs "Looking up address: 0x00000000ffffffff in the debug information...not found.", which isn't what I wanted it to look up anyway...)



The odd thing is that I did get atos to work just fine (with the exact same project.pbxproj) when I force a crash by adding a printf((char*)1) to the otherwise unchanged source code. Why would it work with the build I just made this morning, but not the copy of the build I sent out last week? Does atos break if the executable/ symbols are moved from the original build path? I need a reliable way of getting symbol information for released products.


thanks,
-natevw
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@apple.com


This email sent to email@hidden



When you build with a dSYM, the symbol table is still in the binary unless you manually run strip. If atos finds entries in the symbol table, it will use those unless it finds entries in the dSYM.


Xcode 3.1 is required for atos to load symbol names from the dSYM. In Xcode 3.0, it will only use the dSYM for source line information.

A few things you can check:
- Run dwarfdump --debug-info. It should spew lots of data including symbol names.
- See if your debug build has the symbol table present with nm
- Try using atos from Xcode 3.1 or later


--
Rick Altherr
Architecture and Performance Group
email@hidden


Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: Nothing (reliably) helpful from atos + dSYM
      • From: Nathan Vander Wilt <email@hidden>
References: 
 >Nothing (reliably) helpful from atos + dSYM (From: Nathan Vander Wilt <email@hidden>)

  • Prev by Date: Re: get rid of warning "suggest parenthesis around assignment used as truth value"
  • Next by Date: Re: Nothing (reliably) helpful from atos + dSYM
  • Previous by thread: Nothing (reliably) helpful from atos + dSYM
  • Next by thread: Re: Nothing (reliably) helpful from atos + dSYM
  • Index(es):
    • Date
    • Thread