From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>, gdb@sources.redhat.com
Subject: Re: annota1.exp testsuite failures
Date: Tue, 09 Jan 2007 14:25:00 -0000 [thread overview]
Message-ID: <20070109142532.GA17975@nevyn.them.org> (raw)
In-Reply-To: <20070109033308.GA3663@nevyn.them.org>
On Mon, Jan 08, 2007 at 10:33:08PM -0500, Daniel Jacobowitz wrote:
> On Tue, Jan 09, 2007 at 03:01:06PM +1300, Nick Roberts wrote:
> >
> > The last changes (2006/12/31) to annota1.exp make it fail for me:
>
> It passed for you before then, right? Please send me the full log and
> I'll try to figure out how it changed.
Whoops. Classic mistake on my part. Nick, could you let me know if
this fixes it?
--
Daniel Jacobowitz
CodeSourcery
2007-01-09 Daniel Jacobowitz <dan@codesourcery.com>
* gdb.base/annota1.exp: Remove extra send_gdb.
Index: testsuite/gdb.base/annota1.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota1.exp,v
retrieving revision 1.21
diff -u -p -r1.21 annota1.exp
--- testsuite/gdb.base/annota1.exp 31 Dec 2006 20:01:25 -0000 1.21
+++ testsuite/gdb.base/annota1.exp 9 Jan 2007 14:24:11 -0000
@@ -244,7 +244,6 @@ set pat_begin "\r\n\032\032post-prompt\r
set pat_adjust "warning: Breakpoint 3 address previously adjusted from $hex to $hex.\r\n"
set pat_end "\r\n\032\032breakpoint 3\r\n\r\nBreakpoint 3, \r\n\032\032frame-begin 0 $hex\r\n\r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*.*\032\032frame-function-name\r\n.*printf\r\n\032\032frame-args\r\n.*\032\032frame-end\r\n\r\n\032\032stopped\r\n$gdb_prompt$"
-send_gdb "continue\n"
gdb_test_multiple "continue" "continue to printf" {
-re "${pat_begin}($pat_adjust)?$pat_end" {
pass "continue to printf"
next prev parent reply other threads:[~2007-01-09 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 2:01 Nick Roberts
2007-01-09 3:33 ` Daniel Jacobowitz
2007-01-09 14:25 ` Daniel Jacobowitz [this message]
2007-01-09 22:08 ` Nick Roberts
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=20070109142532.GA17975@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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