This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [cygwin/mingw32] DBX_REGISTER_NUMBER vs DWARF2_FRAME_REF_OUT
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: dannysmith at clear dot net dot nz
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 26 Jul 2006 23:33:35 +0200 (CEST)
- Subject: Re: [cygwin/mingw32] DBX_REGISTER_NUMBER vs DWARF2_FRAME_REF_OUT
- References: <000001c6aeab$dc5d9900$c26d65da@anykey>
> Date: Mon, 24 Jul 2006 11:00:55 +1200
> From: Danny Smith <dannysmith@clear.net.nz>
>
> Any other ideas? What is likely GDB fallout?
GDB by default uses the SVR4 register numbering for DWARF & DWARF 2,
and the old dbx register numbering scheme for other debugging formats
(most notably stabs). Mixing the two is no problem for GDB since can
tell which debugging format it is processing.
But whatever format you chose, make sure the numbering scheme used for
.eh_frame (exception handling) unwind info is the same as .debug_frame
normal DWARF2) unwind info.
The best thing to do is probably to define DWARF2_FRAME_REG_OUT to
always use the SVR4 register map.
Mark