[RFA] gdb_continue_to_breakpoint

[Michael Snyder <msnyder@vmware.com>]

[-- Attachment #1: Type: text/plain, Size: 350 bytes --]

This one-line change affects two changes that make
gdb_continue_to_breakpoint more useful.

1) If we accept "Breakpoint in" as well as "Breakpoint at",
then it will work for non-debug functions.

2) If we accept trailing text after the $location_pattern,
then we are not forced to include a location pattern that
takes us up to the end of the line.


[-- Attachment #2: lib.txt --]
[-- Type: text/plain, Size: 789 bytes --]

2008-09-04  Michael Snyder  <msnyder@vmware.com>

	* lib/gdb.exp (gdb_continue_to_breakpoint): Accept "in" as well
	as "at" (for non-debug functions such as _start).  Also accept
	trailing text after $location_pattern.

Index: lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.105
diff -u -p -r1.105 gdb.exp
--- lib/gdb.exp	15 Aug 2008 15:18:34 -0000	1.105
+++ lib/gdb.exp	4 Sep 2008 20:47:58 -0000
@@ -456,7 +456,7 @@ proc gdb_continue_to_breakpoint {name {l
 
     send_gdb "continue\n"
     gdb_expect {
-	-re "Breakpoint .* at $location_pattern\r\n$gdb_prompt $" {
+	-re "Breakpoint .* (at|in) $location_pattern.*$gdb_prompt $" {
 	    pass $full_name
 	}
 	-re ".*$gdb_prompt $" {