From: kazu@codesourcery.com (Kazu Hirata)
To: gdb-patches@sourceware.org
Subject: [patch] gdb.base/*.exp: Do not expect full paths to file names.
Date: Sat, 31 Jul 2010 00:03:00 -0000 [thread overview]
Message-ID: <20100731000339.F14B15664F4@henry1.codesourcery.com> (raw)
Hi,
Attached is a patch to adjust break-always.exp and commands.exp to
stop expecting full paths to file names.
Without this patch, these testcases fail on sparc-solaris2.8.
Tested on sparc-solaris2.8. OK to apply?
Kazu Hirata
2010-07-30 Kazu Hirata <kazu@codesourcery.com>
* gdb.base/break-always.exp: Do not expect full paths to file
names.
* gdb.base/commands.exp: Likewise.
Index: gdb/testsuite/gdb.base/break-always.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/break-always.exp,v
retrieving revision 1.5
diff -u -d -p -r1.5 break-always.exp
--- gdb/testsuite/gdb.base/break-always.exp 1 Jun 2010 21:29:21 -0000 1.5
+++ gdb/testsuite/gdb.base/break-always.exp 30 Jul 2010 21:47:45 -0000
@@ -29,7 +29,7 @@ gdb_test "show breakpoint always-inserte
runto foo
gdb_test "break bar" "Breakpoint 2.*" "set breakpoint on bar"
-gdb_continue_to_breakpoint "bar" ".*/break-always.c:$bar_location.*"
+gdb_continue_to_breakpoint "bar" ".*break-always.c:$bar_location.*"
Index: gdb/testsuite/gdb.base/commands.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/commands.exp,v
retrieving revision 1.40
diff -u -d -p -r1.40 commands.exp
--- gdb/testsuite/gdb.base/commands.exp 10 Jun 2010 19:48:19 -0000 1.40
+++ gdb/testsuite/gdb.base/commands.exp 30 Jul 2010 21:47:45 -0000
@@ -427,7 +427,7 @@ proc bp_deleted_in_command_test {} {
# Create a breakpoint, and associate a command-list to it, with
# one command that deletes this breakpoint.
gdb_test "break factorial" \
- "Breakpoint \[0-9\]+ at .*: file .*/run.c, line \[0-9\]+\." \
+ "Breakpoint \[0-9\]+ at .*: file .*run.c, line \[0-9\]+\." \
"breakpoint in bp_deleted_in_command_test"
gdb_test_multiple "commands" "begin commands in bp_deleted_in_command_test" {
@@ -489,7 +489,7 @@ proc temporary_breakpoint_commands {} {
# This test will verify that this commands list is executed when the
# breakpoint is hit.
gdb_test "tbreak factorial" \
- "Temporary breakpoint \[0-9\]+ at .*: file .*/run.c, line \[0-9\]+\." \
+ "Temporary breakpoint \[0-9\]+ at .*: file .*run.c, line \[0-9\]+\." \
"breakpoint in temporary_breakpoint_commands"
gdb_test_multiple "commands" \
@@ -634,7 +634,7 @@ proc if_commands_test {} {
}
}
gdb_test_multiple "end" "second end - $test" {
- -re "Breakpoint \[0-9\]+ at .*: file .*/run.c, line \[0-9\]+\.\r\n$gdb_prompt $" {
+ -re "Breakpoint \[0-9\]+ at .*: file .*run.c, line \[0-9\]+\.\r\n$gdb_prompt $" {
pass "second end - $test"
}
-re "Undefined command: \"silent\".*$gdb_prompt $" {
@@ -660,7 +660,7 @@ proc if_commands_test {} {
}
}
gdb_test_multiple "end" "second end - $test" {
- -re "Breakpoint \[0-9\]+ at .*: file .*/run.c, line \[0-9\]+\.\r\n$gdb_prompt $" {
+ -re "Breakpoint \[0-9\]+ at .*: file .*run.c, line \[0-9\]+\.\r\n$gdb_prompt $" {
pass "second end - $test"
}
}
next reply other threads:[~2010-07-31 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 0:03 Kazu Hirata [this message]
2010-08-02 11:46 ` Pedro Alves
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=20100731000339.F14B15664F4@henry1.codesourcery.com \
--to=kazu@codesourcery.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).