This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[commit] Fix gdb.arch/alpha-step.exp


On my new OpenBSD/alpha systems "x /i $pc" doesn't always print
something that has trailing spaces or tabs.  This removes them from
the regular expressions.

Comitted as obvious,

Mark

Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/ChangeLog,v
retrieving revision 1.1231
diff -u -p -r1.1231 ChangeLog
--- ChangeLog	7 Jul 2006 12:53:47 -0000	1.1231
+++ ChangeLog	7 Jul 2006 23:08:10 -0000
@@ -1,3 +1,8 @@
+2006-07-08  Mark Kettenis  <kettenis@gnu.org>
+
+	* gdb.arch/alpha-step.exp (test_stepi): Do not include trailing
+	spaces/tabs in regular expressions since they might not be there.
+
 2006-07-07  Andrew Stubbs  <andrew.stubbs@st.com>
 
 	* gdb.base/ifelse.exp: New file.
Index: gdb.arch/alpha-step.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.arch/alpha-step.exp,v
retrieving revision 1.1
diff -u -p -r1.1 alpha-step.exp
--- gdb.arch/alpha-step.exp	29 May 2005 01:58:52 -0000	1.1
+++ gdb.arch/alpha-step.exp	7 Jul 2006 23:08:10 -0000
@@ -63,7 +63,7 @@ proc test_stepi {function } {
     # Extra check to make sure we stopped on the FP branch instruction.
     
     gdb_test "x /i \$pc" \
-             "0x\[0-9a-fA-F\]+ <.*>:\[ \t\]+fb$function\[ \t\]+.*" \
+             "0x\[0-9a-fA-F\]+ <.*>:\[ \t\]+fb$function.*" \
              "Check breakpoint on fb$function instruction (first call)"
     
     # Step test, followed by the check that we landed on the expected
@@ -75,7 +75,7 @@ proc test_stepi {function } {
              "stepi on fb$function (first call)"
     
     gdb_test "x /i \$pc" \
-             "0x\[0-9a-fA-F\]+ <.*>:\[ \t\]+ret\[ \t\]+.*" \
+             "0x\[0-9a-fA-F\]+ <.*>:\[ \t\]+ret.*" \
              "Check stepi over fb$function stopped on ret"
     
     # Continue again. FUNCTION should be called a second time, this time
@@ -88,7 +88,7 @@ proc test_stepi {function } {
     # Extra check to make sure we stopped on the FP branch instruction.
     
     gdb_test "x /i \$pc" \
-             "0x\[0-9a-fA-F\]+ <.*>:\[ \t\]+fb$function\[ \t\]+.*" \
+             "0x\[0-9a-fA-F\]+ <.*>:\[ \t\]+fb$function.*" \
              "Check breakpoint on fb$function instruction (second call)"
     
     # Step test, branch should not be taken.
@@ -100,7 +100,7 @@ proc test_stepi {function } {
     # Extra check to verify that we landed on the instruction we expected.
     
     gdb_test "x /i \$pc" \
-             "0x\[0-9a-fA-F\]+ <.*>:\[ \t\]+fneg\[ \t\]+.*" \
+             "0x\[0-9a-fA-F\]+ <.*>:\[ \t\]+fneg.*" \
              "Check stepi over fb$function stopped on fneg instruction"
 
 }


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]