From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Adjust step-bt testcase
Date: Thu, 10 Aug 2006 15:21:00 -0000 [thread overview]
Message-ID: <20060810130532.GA18475@nevyn.them.org> (raw)
In-Reply-To: <20060810041258.GD15936@adacore.com>
On Wed, Aug 09, 2006 at 09:12:58PM -0700, Joel Brobecker wrote:
> Hello Daniel,
>
> re: http://www.sourceware.org/ml/gdb/2006-08/msg00079.html
>
> Would the attached patch fix your problem?
Nope - the "in" is apparently optional too. I tested and committed
this variant.
--
Daniel Jacobowitz
CodeSourcery
2006-08-10 Joel Brobecker <brobecker@adacore.com>
Daniel Jacobowitz <dan@codesourcery.com>
* gdb.base/step-bt.exp: Make hexadecimal address optional in
expected output of the backtrace commands.
Index: step-bt.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/step-bt.exp,v
retrieving revision 1.1
diff -u -p -r1.1 step-bt.exp
--- step-bt.exp 8 Aug 2006 21:50:54 -0000 1.1
+++ step-bt.exp 10 Aug 2006 13:03:19 -0000
@@ -63,7 +63,7 @@ gdb_test "stepi" \
"step first instruction"
gdb_test "bt" \
- "#0 +0x\[0-9a-z\]+ in hello .*#1 +0x\[0-9a-z\]* in main.*" \
+ "#0 +(0x\[0-9a-z\]+ in )?hello .*#1 +(0x\[0-9a-z\]* in )?main.*" \
"backtrace after first instruction step"
gdb_test "stepi" \
@@ -71,6 +71,6 @@ gdb_test "stepi" \
"step second instruction"
gdb_test "bt" \
- "#0 +0x\[0-9a-z\]+ in hello .*#1 +0x\[0-9a-z\]* in main.*" \
+ "#0 +(0x\[0-9a-z\]+ in )?hello .*#1 +(0x\[0-9a-z\]* in )?main.*" \
"backtrace after second instruction step"
next prev parent reply other threads:[~2006-08-10 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 13:05 Joel Brobecker
2006-08-10 15:21 ` Daniel Jacobowitz [this message]
2006-08-10 15:22 ` Joel Brobecker
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=20060810130532.GA18475@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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