Re: [patch 1/3] Clear stale specific locs, not whole bpts [rediff]

[Jan Kratochvil <jan dot kratochvil at redhat dot com>]

On Fri, 11 Jun 2010 18:24:40 +0200, Ulrich Weigand wrote:
> This fails on platforms that do not support non-stop mode:
> 
> (gdb) set non-stop on^M
> (gdb) PASS: gdb.base/moribund-step.exp: set non-stop on
> delete breakpoints^M
> (gdb) info breakpoints^M
> No breakpoints or watchpoints.^M
> (gdb) break main^M
> Breakpoint 1 at 0x18c: file /home/uweigand/fsf/gdb-head/gdb/testsuite/gdb.base/start.c, line 34.^M
> (gdb) run ^M
> The target does not support running in non-stop mode.^M
> (gdb) FAIL: gdb.base/moribund-step.exp: running to main in runto

I see now lib/mi-support.exp catches:
        -re "\\^error,msg=\"The target does not support running in non-stop mode.\"" {
            unsupported "Non-stop mode not supported"
            return -1
        }
while CLI lib/gdb.exp so far has not.

OK to check-in?

Tested on x86 opensolaris.


Thanks,
Jan


2010-06-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* lib/gdb.exp (gdb_run_cmd): Return on $gdb_prompt.
	(runto): Catch "The target does not support running in non-stop mode.".

--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -290,6 +290,9 @@ proc gdb_run_cmd {args} {
 	    exp_continue
 	}
 	-notransfer -re "Starting program: \[^\r\n\]*" {}
+	-notransfer -re "$gdb_prompt $" {
+	    # There is no more input expected.
+	}
     }
 }
 
@@ -416,6 +419,10 @@ proc runto { function args } {
 	-re "Breakpoint \[0-9\]*, \[0-9xa-f\]* in .*$gdb_prompt $" { 
 	    return 1
 	}
+	-re "The target does not support running in non-stop mode.\r\n$gdb_prompt $" {
+	    unsupported "Non-stop mode not supported"
+	    return 0
+	}
 	-re "$gdb_prompt $" { 
 	    fail "running to $function in runto"
 	    return 0