This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC stack backtraces


On Thu, Aug 30, 2012 at 1:04 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 08/29/2012 09:22 AM, Ian Lance Taylor wrote:
>
>> It uses the GCC unwind interface to collect a stack trace, and parses
>> DWARF debug info to get file/line/function information.  (Of course it's
>> silly to write yet another DWARF reader, but I didn't find an existing
>> reader that seemed wholly suitable.)  The code currently only works for
>> ELF/DWARF, but it's designed to support other object file and debug
>> formats should anybody care to write them.  Since its use in GCC would
>> be purely for GCC developers, it's not essential that it be fully
>> portable.
>
>
> Sorry for not actually testing the patch, but does it handle inline
> functions?  ("addr2line -i" can print multiple source locations for a single
> stack frame.)

Yes.

> Support for /usr/lib/debug would be desirable, too.

That is not there.  I haven't looked into what this requires.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]