From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Problem with new step-bt test?
Date: Wed, 09 Aug 2006 22:05:00 -0000 [thread overview]
Message-ID: <20060809220456.GA2781@nevyn.them.org> (raw)
(gdb) PASS: gdb.base/step-bt.exp: step second instruction
bt
#0 hello () at /space/fsf/commit/src/gdb/testsuite/gdb.base/step-bt.c:27
#1 0x00000000004004d1 in main () at
/space/fsf/commit/src/gdb/testsuite/gdb.base/step-bt.c:33
(gdb) FAIL: gdb.base/step-bt.exp: backtrace after second instruction step
testcase /space/fsf/commit/src/gdb/testsuite/gdb.base/step-bt.exp completed
in 2 seconds
I figure that ought to be a PASS output, right? I think the problem is that
the two hex patterns need to be optional, but I haven't tried it.
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2006-08-09 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 22:05 Daniel Jacobowitz [this message]
2006-08-09 23:40 ` Joel Brobecker
2006-08-10 0:28 ` 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=20060809220456.GA2781@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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