Make dprintf-non-stop.exp cope with remote testing
authorPedro Alves <palves@redhat.com>
Mon, 30 Nov 2015 16:05:19 +0000 (16:05 +0000)
committerPedro Alves <palves@redhat.com>
Mon, 30 Nov 2015 18:40:07 +0000 (18:40 +0000)
commit09df4675f2e4f8f098954f9a38f44d12089f1c4e
treea80fcd74e40003df85edc07150f309f1a8aae24c
parent56cf4bed5354769d7352c5cf4e054a346d2553cd
Make dprintf-non-stop.exp cope with remote testing

Testing with the extended-remote board with "maint set target-non-stop
on" shows a dprintf-non-stop.exp regression.  The issue is simply that
the test is expecting output that is only valid for the native target:

 native:

  [process 8676] #1 stopped.

 remote:

  [Thread 8900.8900] #1 stopped.

In order to expose this without "maint set target-non-stop on", this
restarts gdb with non-stop mode already enabled.

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

* gdb.base/dprintf-non-stop.exp: Use build_executable instead of
prepare_for_testing.  Start gdb with "set non-stop on" appended to
GDBFLAGS.  Lax expected stop output.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/dprintf-non-stop.exp