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]

[patch] Fix testsuite/gdb.arch/altivec-abi.exp


After a GDB finish command, 'altivec-abi.exp' seems to expect some like this:
	Run till exit from #0  0x0804835f in marker ()
But the '0x0804835f in' is only printed if the target program was compiled without -g.

This patch makes altivec-abi.exp stop expecting the 'in':

2005-08-12  Paul Gilliam  <pgilliam@us.ibm.com>

	* gdb.arch/altivec-abi.exp: Elide the 'in' from what's expected after a 'finish' command.


diff -a -u -r1.5 altivec-abi.exp
--- testsuite/gdb.arch/altivec-abi.exp  3 May 2005 00:41:48 -0000       1.5
+++ testsuite/gdb.arch/altivec-abi.exp  12 Sep 2005 23:47:18 -0000
@@ -75,7 +75,7 @@

 gdb_test "b marker" "Breakpoint 2 at.*file.*altivec-abi.c, line \[0-9\]+." "break marker"
 gdb_test "continue" "Breakpoint 2.*marker.*altivec-abi.c.*" "continue to marker"
-gdb_test "finish" "Run till exit from .0.*in marker.*at.*altivec-abi.c.*main \\(\\) at.*altivec-abi.c.*result = vec_func \\(vshort,.*goes in v2.*" "back to main (1)"
+gdb_test "finish" "Run till exit from .0.*marker.*at.*altivec-abi.c.*main \\(\\) at.*altivec-abi.c.*result = vec_func \\(vshort,.*goes in v2.*" "back to main (1)"

 # now all the arguments of vec_fun are initialized

@@ -100,7 +100,7 @@
   "step into vec_fun"

 set pattern2 $pattern
-append pattern2 " at.*altivec-abi.c.*in main.*result = vec_func .vshort,.*goes in v2.*Value returned is.*= .2, 2, 2, 2."
+append pattern2 " at.*altivec-abi.c.*main.*result = vec_func .vshort,.*goes in v2.*Value returned is.*= .2, 2, 2, 2."

 # Let's see if the result is returned correctly.
 gdb_test "finish" \


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