Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Use Dwarf 2 CFI on PowerPC targets
Date: Sun, 27 Mar 2005 00:40:00 -0000	[thread overview]
Message-ID: <je4qexj4zx.fsf@sykes.suse.de> (raw)
In-Reply-To: <20050326224408.GB1151@nevyn.them.org> (Daniel Jacobowitz's message of "Sat, 26 Mar 2005 17:44:08 -0500")

Daniel Jacobowitz <drow@false.org> writes:

> On Wed, Sep 08, 2004 at 10:43:27AM -0500, Jim Blandy wrote:
>> 
>> This works fine on PowerPC E500 Linux; I'm still testing it on other
>> platforms.  Thus it's a Request for Comments, not Approval.  I'll be
>> back with test results on AIX, sim, and plain PowerPC Linux in a bit.
>> 
>> 2004-09-02  Jim Blandy  <jimb@redhat.com>
>> 
>> 	* rs6000-tdep.c: #include "dwarf2-frame.h".
>> 	(rs6000_dwarf2_reg_to_regnum): Recognize 65 as another number for lr.
>> 	(rs6000_gdbarch_init): Hook in dwarf2_frame_sniffer.
>> 	* Makefile.in (rs6000-tdep.o): Update dependencies.
>
> Did you ever finish testing these?  There are now twelve targets which
> use dwarf2_frame_sniffer and I've just posted a patch to enable it for
> another, but PPC is still behind.

I've tested the patch with current HEAD on powerpc-suse-linux, and there
are 73 regressions and 17 progressions.

+FAIL: gdb.base/corefile.exp: backtrace in corefile.exp
-FAIL: gdb.base/gcore.exp: where in corefile (pattern 2)
+FAIL: gdb.base/funcargs.exp: backtrace from call6c (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call6d (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call6e (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call6f (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call6g (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call6h (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call6i (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call6j (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call6k (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7c (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7d (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7e (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7f (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7g (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7h (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7i (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7j (pattern 3)
+FAIL: gdb.base/funcargs.exp: backtrace from call7k (pattern 3)
+FAIL: gdb.base/funcargs.exp: recursive passing of structs by value (pattern 8 + sentinel)
+FAIL: gdb.base/gcore.exp: where in corefile (pattern 3)
-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/sigbpt.exp: stepi; stepi out of handler
-FAIL: gdb.base/sigbpt.exp: stepi bp before segv; stepi out of handler
-FAIL: gdb.base/sigbpt.exp: stepi bp at segv; stepi out of handler
-FAIL: gdb.base/sigbpt.exp: stepi bp before and at segv; stepi out of handler
-FAIL: gdb.base/sigstep.exp: stepi from handleri; leave handler
-FAIL: gdb.base/sigstep.exp: nexti from handleri; leave handler
+FAIL: gdb.base/langs.exp: backtrace in langs.exp
+FAIL: gdb.base/langs.exp: up to cppsub_ in langs.exp
+FAIL: gdb.base/langs.exp: up to fsub in langs.exp
+FAIL: gdb.base/langs.exp: show language at fsub in langs.exp
+FAIL: gdb.base/langs.exp: up to langs0__2do in langs.exp
+FAIL: gdb.base/langs.exp: show language at langs0__2do in langs.exp
+FAIL: gdb.base/langs.exp: up to main in langs.exp
+FAIL: gdb.base/savedregs.exp: Check dummy info frame; stack contains callee caller dummy catcher sigtramp thrower main
+FAIL: gdb.base/sigaltstack.exp: backtrace (pattern 4)
+FAIL: gdb.base/sigaltstack.exp: finish to catch INNER (the program exited)
+FAIL: gdb.base/sigaltstack.exp: finish from catch INNER
+FAIL: gdb.base/sigaltstack.exp: finish to OUTER
+FAIL: gdb.base/sigaltstack.exp: finish to catch MAIN
+FAIL: gdb.base/sigaltstack.exp: finish to MAIN
+FAIL: gdb.cp/classes.exp: print (int)pmi == sizeof(int)
+FAIL: gdb.cp/classes.exp: print bar.st
+FAIL: gdb.cp/classes.exp: print *$
+FAIL: gdb.cp/classes.exp: print csi without static members
+FAIL: gdb.cp/classes.exp: print cnsi without static members
+FAIL: gdb.cp/classes.exp: print csi with static members
+FAIL: gdb.cp/classes.exp: print cnsi with static members
+FAIL: gdb.cp/classes.exp: continue (the program is no longer running)
+FAIL: gdb.cp/classes.exp: finish from marker_reg1
+FAIL: gdb.cp/classes.exp: calling method for small class
+FAIL: gdb.mi/mi-stack.exp: stack frame listing
+FAIL: gdb.mi/mi-stack.exp: stack frame listing 1 1
+FAIL: gdb.mi/mi-stack.exp: stack frame listing 1 3
+FAIL: gdb.mi/mi-stack.exp: stack args listing 0
+FAIL: gdb.mi/mi-stack.exp: stack args listing 0 1 3
+FAIL: gdb.mi/mi-stack.exp: stack args listing 1
+FAIL: gdb.mi/mi-stack.exp: stack args listing 1 1 3
+FAIL: gdb.mi/mi-stack.exp: stack info-depth
+FAIL: gdb.mi/mi-syn-frame.exp: 407-stack-list-frames
+FAIL: gdb.mi/mi-syn-frame.exp: 408-exec-continue
+FAIL: gdb.mi/mi-syn-frame.exp: 409-stack-list-frames 0 0
+FAIL: gdb.mi/mi-syn-frame.exp: backtrace from inferior function at exception
+FAIL: gdb.mi/mi2-stack.exp: stack frame listing
+FAIL: gdb.mi/mi2-stack.exp: stack frame listing 1 1
+FAIL: gdb.mi/mi2-stack.exp: stack frame listing 1 3
+FAIL: gdb.mi/mi2-stack.exp: stack args listing 0
+FAIL: gdb.mi/mi2-stack.exp: stack args listing 0 1 3
+FAIL: gdb.mi/mi2-stack.exp: stack args listing 1
+FAIL: gdb.mi/mi2-stack.exp: stack args listing 1 1 3
+FAIL: gdb.mi/mi2-stack.exp: stack info-depth
+FAIL: gdb.mi/mi2-syn-frame.exp: 407-stack-list-frames
+FAIL: gdb.mi/mi2-syn-frame.exp: 408-exec-continue
+FAIL: gdb.mi/mi2-syn-frame.exp: 409-stack-list-frames 0 0
+FAIL: gdb.mi/mi2-syn-frame.exp: backtrace from inferior function at exception
-FAIL: gdb.threads/gcore-thread.exp: corefile contains at least two threads
-FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 1
+FAIL: gdb.threads/linux-dp.exp: first thread-specific breakpoint hit
-FAIL: gdb.threads/pthreads.exp: check backtrace from main thread
-FAIL: gdb.threads/pthreads.exp: check backtrace from thread 1
-FAIL: gdb.threads/pthreads.exp: apply backtrace command to all three threads
-FAIL: gdb.threads/schedlock.exp: thread 2 ran (didn't run)
+FAIL: gdb.threads/pthread_cond_wait.exp: backtrace in blocked thread
+FAIL: gdb.threads/schedlock.exp: thread 3 ran (didn't run)

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2005-03-27  0:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 15:44 Jim Blandy
2005-03-26 22:43 ` Daniel Jacobowitz
2005-03-27  0:40   ` Andreas Schwab [this message]
2005-03-29 17:42     ` Jim Blandy
2005-03-29 21:45       ` Andreas Schwab

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=je4qexj4zx.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    /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