aboutsummaryrefslogtreecommitdiff
path: root/ld
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2015-07-29 16:24:53 +0100
committerPedro Alves <palves@redhat.com>2015-07-29 16:24:53 +0100
commit1eef6428112a1c1fe0295f36f92d7a3cf9908228 (patch)
treef1754fa39db17c72891e26cd69dc9a6261a73e29 /ld
parent7da5b897c96faa3c520662d2b0bd4837567bfb1d (diff)
downloadfsf-binutils-gdb-1eef6428112a1c1fe0295f36f92d7a3cf9908228.zip
fsf-binutils-gdb-1eef6428112a1c1fe0295f36f92d7a3cf9908228.tar.gz
fsf-binutils-gdb-1eef6428112a1c1fe0295f36f92d7a3cf9908228.tar.bz2
Make gdb.base/multi-forks.exp work with the native-extended-gdbserver board
Now that we can expect inferior output with the gdbserver boards, this is all it takes to have the test pass against extended-remote gdbserver. Don Breazeal originally wrong something like this: https://sourceware.org/ml/gdb-patches/2015-03/msg00506.html which was what originally inspired the introduction of $inferior_spawn_id. gdb/testsuite/ChangeLog: 2015-07-29 Pedro Alves <palves@redhat.com> Don Breazeal <donb@codesourcery.com> * gdb.base/multi-forks.exp (continue_to_exit_bp_loc): Expect output from both inferior_spawn_id and gdb_spawn_id.
Diffstat (limited to 'ld')
0 files changed, 0 insertions, 0 deletions