This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[COMMIT] Obvious fix to Obvious fix
- From: Paul Gilliam <pgilliam at us dot ibm dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Mon, 17 Oct 2005 15:21:03 -0700
- Subject: [COMMIT] Obvious fix to Obvious fix
- Reply-to: pgilliam at us dot ibm dot com
Boy, is my face red.
I made an obvious fix a while back that was wrong: A pattern in altivec-regs.exp looked like it needed spaces,
but the actual test output had a tab. I thought I had tested it, but must not have. 8-(
This time, I'm sure.
2005-10-17 Paul Gilliam <pgilliam@us.ibm.com>
* gdb.arch/altivec-regs.exp: Adjust "info reg vrsave" and "info reg
vscr" tests to better match output.
Index: altivec-regs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.arch/altivec-regs.exp,v
retrieving revision 1.8
diff -a -u -p -r1.8 altivec-regs.exp
--- altivec-regs.exp 19 Sep 2005 18:09:08 -0000 1.8
+++ altivec-regs.exp 17 Oct 2005 22:07:17 -0000
@@ -113,8 +113,8 @@ for {set i 0} {$i < 32} {incr i 1} {
gdb_test "info reg vr$i" "vr$i.*$vector_register" "info reg vr$i"
}
-gdb_test "info reg vrsave" "vrsave.*0x1 +1" "info reg vrsave"
-gdb_test "info reg vscr" "vscr.*0x1 +1" "info reg vscr"
+gdb_test "info reg vrsave" "vrsave.*0x1\[\t \]+1" "info reg vrsave"
+gdb_test "info reg vscr" "vscr.*0x1\[\t \]+1" "info reg vscr"
# Now redo the same tests, but using the print command.
# Note: in LE case, the char array is printed WITHOUT the last character.