Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Cc: cagney@redhat.com
Subject: Re: New test failures - observer.exp, sigaltstack.exp, siginfo.exp
Date: Fri, 16 Apr 2004 17:02:00 -0000	[thread overview]
Message-ID: <20040416161820.GA14175@nevyn.them.org> (raw)
In-Reply-To: <20040416151243.GA31255@nevyn.them.org>

On Fri, Apr 16, 2004 at 11:12:43AM -0400, Daniel Jacobowitz wrote:
> siginfo.exp fails like this:
> (gdb) PASS: gdb.base/siginfo.exp: continue to stepi handler
> bt
> #0  handler (sig=26, info=0xbfffeda0, context=0xbfffee20) at /opt/src/gdb/src/gdb/testsuite/gdb.base/siginfo.c:31
> #1  <signal handler called>
> #2  main () at /opt/src/gdb/src/gdb/testsuite/gdb.base/siginfo.c:66
> (gdb) PASS: gdb.base/siginfo.exp: backtrace for nexti
> step
> 32      } /* handler */
> 1: x/i $pc  0x8048411 <handler+13>:     pop    %ebp
> (gdb) step
> 
> Program exited normally.
> (gdb) FAIL: gdb.base/siginfo.exp: step out of handler
> 
> I don't know if this is currently expected, or what.  It seems like a
> bug.

Oh, easy: this is backtrace/1613.  I hadn't caught up on gdb-prs yet.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-04-16 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 16:18 Daniel Jacobowitz
2004-04-16 17:02 ` Daniel Jacobowitz [this message]
2004-04-17 13:52 ` Joel Brobecker
2004-04-20 16:40 ` Andrew Cagney
2004-04-20 21:21   ` Daniel Jacobowitz
2004-05-03 19:21     ` Andrew Cagney
2004-05-04 19:46       ` Daniel Jacobowitz
2004-08-08 21:41         ` Daniel Jacobowitz
2004-08-09 13:20           ` Andrew Cagney
2004-04-24  0:03 ` Andrew Cagney
2004-04-23 18:35   ` Daniel Jacobowitz
2004-04-24  0:03     ` Andrew Cagney

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=20040416161820.GA14175@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@redhat.com \
    --cc=gdb@sources.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