Fix gdb.threads/non-ldr-exc-3.exp race
authorPedro Alves <palves@redhat.com>
Tue, 15 Sep 2015 16:01:59 +0000 (17:01 +0100)
committerPedro Alves <palves@redhat.com>
Tue, 15 Sep 2015 16:01:59 +0000 (17:01 +0100)
commitd15dcecdee0f07b0b088dd3a8ebb50826c5b7bc5
tree9bfdf50db382af61d92ab82ff300b2b1fa7b9275
parent750ce8d1caf237464dd663de54ad055c0e58409d
Fix gdb.threads/non-ldr-exc-3.exp race

gdb.threads/non-ldr-exc-3.exp is sometimes failing like this:

 [Switching to Thread 6831.6832]

 Breakpoint 2, thread_execler (arg=0x0) at /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.threads/non-ldr-exc-3.c:41
 41        if (execl (image, image, argv1, NULL) == -1) /* break-here */
 PASS: gdb.threads/non-ldr-exc-3.exp: lock-sched=on,non-stop=off: continue to breakpoint
 (gdb) set scheduler-locking on
 (gdb) FAIL: gdb.threads/non-ldr-exc-3.exp: lock-sched=on,non-stop=off: set scheduler-locking on

The problem is that the gdb_test_multiple is missing the prompt
anchor.  The problem was introduced by 2fd33e9448.  This reverts the
hunk that introduced the problem, reverting back to
gdb_continue_to_breakpoint.

gdb/testsuite/ChangeLog:
2015-09-15  Pedro Alves  <palves@redhat.com>

* gdb.threads/non-ldr-exc-3.exp (do_test): Use
gdb_continue_to_breakpoint instead of gdb_test_multiple.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/non-ldr-exc-3.exp