diff options
| author | Pedro Alves <palves@redhat.com> | 2014-03-20 13:26:33 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2014-03-20 13:44:32 +0000 |
| commit | 9f5e1e021a843e573b72ee448397a4db139adf2e (patch) | |
| tree | a22c08521185db81a7207db16c1ee0c5d1d5657f /gdb/tui/tui-data.c | |
| parent | 99619beac6252113fed212fdb9e1ab97bface423 (diff) | |
| download | gdb-9f5e1e021a843e573b72ee448397a4db139adf2e.zip gdb-9f5e1e021a843e573b72ee448397a4db139adf2e.tar.gz gdb-9f5e1e021a843e573b72ee448397a4db139adf2e.tar.bz2 | |
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.
Diffstat (limited to 'gdb/tui/tui-data.c')
0 files changed, 0 insertions, 0 deletions