This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: DWARF2 unwinding documentation/help
- From: Richard Henderson <rth at redhat dot com>
- To: Bernardo Innocenti <bernie at develer dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 3 Sep 2003 10:04:32 -0700
- Subject: Re: DWARF2 unwinding documentation/help
- References: <200308241753.28678.bernie@develer.com> <20030825213203.GB19623@redhat.com> <3F55C84F.1030604@develer.com>
On Wed, Sep 03, 2003 at 12:54:07PM +0200, Bernardo Innocenti wrote:
> Binaries are pre/post-processed at the final link stage. The linker
> is replaced by a shell script invoking the real linker with additional
> flags and an "elf2flt" program to convert the result to a flat binary.
Ah hah. In which case I would *keep* all of the compiler-level
features that know about named sections, and simply at the end
use a custom link script to make sure the data winds up in a place
that your elf2flt needs.
One advantage here is that the .eh_frame section remains separate,
and thus readelf can dump it for you.
> Ok. One less thing to worry about. Does the dwarf2 output depend
> on frame size and layout? Does the unwinder need to know where
> registers are being saved on the stack?
Of course.
r~