.eh_frame, .eh_frame_hdr - how to remove that trash
kabaev at gmail.com
Fri Oct 21 22:39:34 UTC 2011
On Fri, 21 Oct 2011 00:54:32 -0700
Garrett Cooper <yanegomi at gmail.com> wrote:
> On Fri, Oct 21, 2011 at 12:51 AM, Wojciech Puchar
> <wojtek at wojtek.tensor.gdynia.pl> wrote:
> >> on entry into each function, which is different from usual x86
> >> convention.
> >> Asynchronous unwind info (yeah, same stuff you keep referring to as
> >> crap), is the only way you can debug your program or get anything
> >> remotely close to usable backtrace, by default.
> > i understand but i DO NOT called compiler with -g option which
> > clearly means that i do not want to debug isn't it?
> It seems like a binutils bug (or somewhere in that immediate
> neighborhood) because all debugging related sections should be
> stripped out by strip including unwind, correct?
NO. Unwind info is a part of the ABI, and its relationship to debug
flags as well as to wishes of the OP is very remote.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 188 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20111021/7b868afd/signature.pgp
More information about the freebsd-hackers