Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: symbols, stripping, and crash logs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: symbols, stripping, and crash logs

Subject: Re: symbols, stripping, and crash logs
From: "James W. Walker" <email@hidden>
Date: Tue, 11 Apr 2006 13:56:27 -0700

I asked:

 Is there any GCC option that could be used to turn off
per-function symbols on individual source files?  You know, so that
a few functions like CheckCopyProtection could be hidden.


Lawrence Gold <email@hidden> wrote:

None that I know of. I've found the best option is to include debug symbols, and then strip them before you ship. Although the crash logs can't be eyeballed, you can use atos against an unstripped build to interpret them, and you get the bonus of line numbers and source file names. As far as I know, if you use only per-function symbols, you only get the name of the function in the backtrace, but not where in the function the problem occurred.


OK, thanks, I'll consider that.
--
  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



Prev by Date:
Re: Debugger stepping into incorrect files on intel

Next by Date:
Re: Distributed build Issues

Previous by thread:
Re: symbols, stripping, and crash logs

Next by thread:
OpenGL

Index(es):

Date
Thread