Date: Fri, 21 Oct 2011 00:54:32 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: .eh_frame, .eh_frame_hdr - how to remove that trash Message-ID: <CAGH67wQUe%2BHObUjWq29f6utSN3tcOweK=FQtvGf9vTy7sQa_-Q@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1110210951020.11633@wojtek.tensor.gdynia.pl> References: <alpine.BSF.2.00.1110200937220.33102@wojtek.tensor.gdynia.pl> <20111020082234.GA4568@britannica.bec.de> <alpine.BSF.2.00.1110201244001.36805@wojtek.tensor.gdynia.pl> <4EA00DEF.3030905@FreeBSD.org> <alpine.BSF.2.00.1110210020250.8905@wojtek.tensor.gdynia.pl> <20111020190553.6bf95790@kan.dnsalias.net> <alpine.BSF.2.00.1110210112420.3746@wojtek.tensor.gdynia.pl> <20111020192653.6425f018@kan.dnsalias.net> <alpine.BSF.2.00.1110210951020.11633@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 21, 2011 at 12:51 AM, Wojciech Puchar <wojtek@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? Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wQUe%2BHObUjWq29f6utSN3tcOweK=FQtvGf9vTy7sQa_-Q>