diff options
| author | Simon Marchi <simon.marchi@ericsson.com> | 2016-05-02 13:10:33 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@ericsson.com> | 2016-05-02 13:10:33 -0400 |
| commit | 444e826c911693e6dad1cf907d81eb9dc1bef7d2 (patch) | |
| tree | d6d21389bf3ef8a24a98d6a87f59b07fa95df373 /cpu | |
| parent | 740feeaa2049d0f9a7e5928191124583a1a8c645 (diff) | |
| download | gdb-444e826c911693e6dad1cf907d81eb9dc1bef7d2.zip gdb-444e826c911693e6dad1cf907d81eb9dc1bef7d2.tar.gz gdb-444e826c911693e6dad1cf907d81eb9dc1bef7d2.tar.bz2 | |
Fix detach.exp remote check
This test seems to work with both native-gdbserver and
native-extended-gdbserver, so I removed the remote check.
When running with native-gdbserver (a stub-like target), detach makes
gdbserver stop and gdb disconnect. runto_main just spawns a brand new
gdbserver. So it tests the exact same thing twice. It doesn't hurt
though.
With native-extended-gdbserver, the test is probably a bit more useful
(and similar to native). It tests running/detaching twice using the
same gdb/gdbserver instances, since with extended-remote, you can
detach/attach/run all you want, unlike with remote.
gdb/testsuite/ChangeLog:
* gdb.base/detach.exp: Remove is_remote check.
Diffstat (limited to 'cpu')
0 files changed, 0 insertions, 0 deletions