From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: [ob] Fix gdb.stabs/weird.exp
Date: Wed, 22 Nov 2006 15:25:00 -0000 [thread overview]
Message-ID: <20061122152545.GA3679@nevyn.them.org> (raw)
send_gdb needs \n at the end; gdb_test_multiple, like gdb_test, doesn't.
The extra GDB prompt can cause random test failures.
I should commit this to the branch too. I'll do that after I check
it out.
--
Daniel Jacobowitz
CodeSourcery
2006-11-22 Daniel Jacobowitz <dan@codesourcery.com>
* gdb.stabs/weird.exp (print_weird_var): Don't send extra \n.
Index: gdb.stabs/weird.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.stabs/weird.exp,v
retrieving revision 1.11
diff -u -p -r1.11 weird.exp
--- gdb.stabs/weird.exp 9 Nov 2006 19:31:14 -0000 1.11
+++ gdb.stabs/weird.exp 22 Nov 2006 15:23:25 -0000
@@ -1,4 +1,4 @@
-# Copyright 1997, 1998, 1999, 2001, 2003, 2004
+# Copyright 1997, 1998, 1999, 2001, 2003, 2004, 2006
# Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
@@ -228,7 +228,7 @@ proc print_weird_var { var } {
# Make sure that the variable gets printed out correctly, without
# any sort of warning message.
- gdb_test_multiple "print $var\n" "variable $var printed property" {
+ gdb_test_multiple "print $var" "variable $var printed property" {
-re "^print $var\r*\n.\[0-9\]* = 42.*$gdb_prompt $" {
pass "variable $var printed properly"
}
next reply other threads:[~2006-11-22 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 15:25 Daniel Jacobowitz [this message]
2006-11-22 15:56 ` Mark Kettenis
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=20061122152545.GA3679@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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