From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: Use DWARF CFI frame unwinder on powerpc
Date: Mon, 15 May 2006 16:46:00 -0000 [thread overview]
Message-ID: <20060515161213.GE28924@nevyn.them.org> (raw)
In-Reply-To: <jehd3z1dy7.fsf@sykes.suse.de>
On Tue, May 09, 2006 at 04:16:00PM +0200, Andreas Schwab wrote:
> Together with the previous patch this enables the use of the DWARF CFI
> frame unwinder on powerpc. This fixes the following testsuite failures:
>
> -FAIL: gdb.base/break.exp: next over recursive call
> -FAIL: gdb.base/break.exp: backtrace from factorial(5.1)
> -FAIL: gdb.base/recurse.exp: continue to recurse (a = 4)
> -FAIL: gdb.base/recurse.exp: continue to recurse (a = 3)
> -FAIL: gdb.base/recurse.exp: continue to recurse (a = 2)
> -FAIL: gdb.base/recurse.exp: continue to recurse (a = 1)
> -FAIL: gdb.base/recurse.exp: continue to second instance watchpoint, second time
> -FAIL: gdb.base/recurse.exp: second instance watchpoint deleted when leaving scope
> -FAIL: gdb.base/recurse.exp: continue to first instance watchpoint, second time
> -FAIL: gdb.base/recurse.exp: first instance watchpoint deleted when leaving scope
> -FAIL: gdb.base/sepdebug.exp: next over recursive call
> -FAIL: gdb.base/sepdebug.exp: backtrace from factorial(5.1)
>
> without any new regressions. Tested with powerpc-suse-linux.
>
> Andreas.
>
> 2006-05-09 Andreas Schwab <schwab@suse.de>
>
> * rs6000-tdep.c: Include "dwarf2-frame.h".
> (rs6000_eh_frame_regnum): Define.
> (rs6000_gdbarch_init): Enable use of DWARF CFI frame unwinder.
> Register rs6000_eh_frame_regnum.
>
> * Makefile.in (rs6000-tdep.o): Update dependencies.
Hi Andreas,
I know we tried to do this once before, and ran into hiccups based on
the GCC numbering being inconsistent. Do we know which versions of GCC
this is likely to work with, and which are likely to make it fall down
horribly? I recall that GPRs were OK, but the numbering for LR was
ambiguous.
It might have been this:
2004-01-21 Alan Modra <amodra@bigpond.net.au>
* config/rs6000/sysv4.h (DWARF2_FRAME_REG_OUT): Define.
* dwarf2out.c (output_cfi): Map regs using DWARF2_FRAME_REG_OUT.
* doc/tm.texi (DWARF_FRAME_REGNUM, DWARF2_FRAME_REG_OUT): Document.
Yep, here's Mark K. and Alan discussing it:
http://gcc.gnu.org/ml/gcc/2004-01/msg00025.html
I'm worried that since we don't currently use the "this is the unwind
column" to indicate where lr lives in the table, although we could,
we'll break on pre-3.4-ish(?) binaries.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-15 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 14:16 Andreas Schwab
2006-05-09 17:17 ` PAUL GILLIAM
2006-05-09 17:23 ` Daniel Jacobowitz
2006-05-09 22:26 ` PAUL GILLIAM
2006-05-09 17:46 ` Andreas Schwab
2006-05-09 18:01 ` David S. Miller
2006-05-09 18:39 ` Daniel Jacobowitz
2006-05-09 21:07 ` David S. Miller
2006-05-15 16:46 ` Daniel Jacobowitz [this message]
2006-05-15 19:10 ` Mark Kettenis
2006-05-15 20:43 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060515161213.GE28924@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox