Make signal-while-stepping-over-bp-other-thread.exp run against remote targets too.
authorPedro Alves <palves@redhat.com>
Thu, 20 Mar 2014 13:26:33 +0000 (13:26 +0000)
committerPedro Alves <palves@redhat.com>
Thu, 20 Mar 2014 13:44:32 +0000 (13:44 +0000)
commit9f5e1e021a843e573b72ee448397a4db139adf2e
treea22c08521185db81a7207db16c1ee0c5d1d5657f
parent99619beac6252113fed212fdb9e1ab97bface423
Make signal-while-stepping-over-bp-other-thread.exp run against remote targets too.

Use pthread_kill instead of the host's "kill".  The reason the test
wasn't written that way to begin with, is that done this way, before
the previous fixes to make GDB step-over all other threads before the
stepping thread, the test would fail...

Tested on x86_64 Fedora 17, native and gdbserver.

gdb/testsuite/
2014-03-20  Pedro Alves  <palves@redhat.com>

* gdb.threads/signal-while-stepping-over-bp-other-thread.c (main):
Use pthread_kill to signal thread 2.
* gdb.threads/signal-while-stepping-over-bp-other-thread.exp:
Adjust to make the test send itself a signal rather than using the
host's "kill" command.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.c
gdb/testsuite/gdb.threads/signal-while-stepping-over-bp-other-thread.exp