darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fix detach.exp remote check

Browse source 
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.
This commit is contained in:
Simon Marchi 2016-05-02 13:10:33 -04:00
parent 740feeaa20
commit 444e826c91
2 changed files with 4 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gdb/testsuite/ChangeLog
View file

@ -1,3 +1,7 @@
2016-05-02 Simon Marchi <simon.marchi@ericsson.com>
* gdb.base/detach.exp: Remove is_remote check.
2016-05-02 Simon Marchi <simon.marchi@ericsson.com>
* gdb.base/annota-input-while-running.exp: Don't check for

5
gdb/testsuite/gdb.base/detach.exp
View file

@ -22,11 +22,6 @@ if { ! [istarget "*-*-linux*"] } {
return 0
}
# Are we on a target board?
if [is_remote target] then {
return 0
}
standard_testfile attach.c
set escapedbinfile [string_to_regexp ${binfile}]