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

From: Basile Starynkevitch <basile at starynkevitch dot net>
To: PaweÅ Sikora <pluto at agmk dot net>
Cc: gcc at gcc dot gnu dot org, Ian Lance Taylor <iant at google dot com>
Date: Wed, 29 Aug 2012 10:15:31 +0200
Subject: Re: GCC stack backtraces
References: <mcroblumab4.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <32071968.aQarcMI28X@pawels>

On Wed, Aug 29, 2012 at 10:07:30AM +0200, PaweÅ Sikora wrote:
> On Wednesday 29 of August 2012 00:22:55 Ian Lance Taylor wrote:
> > I've spent the last couple of days working on a stack backtrace library.
> > 
> > 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.)
> 
> isn't the libdwarf a good enough for reading?
> 
> http://reality.sgiweb.org/davea/dwarf.html

If Ian's DWARF reader is simple enough (since suited for a single purpose), 
it might be helpful to avoid yet another external library dependency for GCC.

Regards
-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

Follow-Ups:
- Re: GCC stack backtraces
  - From: Frank Ch. Eigler

References:
- GCC stack backtraces
  - From: Ian Lance Taylor
- Re: GCC stack backtraces
  - From: PaweÅ Sikora

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