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: Interpreting LSDA information

From: Ian Lance Taylor <iant at google dot com>
To: Yaakov Yaari <YAARI at il dot ibm dot com>
Cc: gcc at gcc dot gnu dot org
Date: 29 May 2007 10:04:08 -0700
Subject: Re: Interpreting LSDA information
References: <OF8E2B9089.918ED5C3-ONC22572EA.00492CC6-C22572EA.004B0787@il.ibm.com>

Yaakov Yaari <YAARI@il.ibm.com> writes:

> LSDA (Language Specific Data Area) is used to store exception handling
> information at the exception catch site, see
> http://www.codesourcery.com/cxx-abi/exceptions.pdf.
> 
> For various kinds of binary analyzers (translators, optimizers) it is
> useful to be able to interpret the LSDA of a given C++ function. So, once
> the LSDA extent is identified, are there any tools, scripts, code snippets,
> that can analyze and interpret this LSDA  in a raw byte form and produce a
> textual interpretation of it?

It's probably rather more simple minded than you want, but you can get
a dump of sorts by using readelf --debug-dump=frames.

Ian

References:
- Interpreting LSDA information
  - From: Yaakov Yaari

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