OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Skip gdb.threads/thread_events.exp on RSP targets properly 

Fixes, with --target_board=native-extended-gdbserver:

  Running ..../src/gdb/testsuite/gdb.threads/thread_events.exp ...
  FAIL: gdb.threads/thread_events.exp: continue to after_join_func with messages enabled (saw 0, expected 1)

gdb/testsuite/ChangeLog:
2017-10-13  Pedro Alves  <palves@redhat.com>

	* gdb.threads/thread_events.exp: Check gdb_protocol instead of
	is_remote.
This commit is contained in:
Pedro Alves 2017-10-13 12:18:50 +01:00
parent df479dc6e0
commit d7bcd5b8e5
2 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,8 @@
2017-10-13 Pedro Alves <palves@redhat.com>
* gdb.threads/thread_events.exp: Check gdb_protocol instead of
is_remote.
2017-10-13 Pedro Alves <palves@redhat.com>
* gdb.base/corefile.exp (corefile_test_run): Skip if gdb_protocol

7
gdb/testsuite/gdb.threads/thread_events.exp
View File

@ -27,9 +27,10 @@ if ![istarget *-*-linux*] then {
return
}
# When using gdbserver, even on Linux, we don't get notifications
# about new threads. This is expected, so don't test for that.
if [is_remote target] then {
# When using the RSP, we don't get notifications about new threads.
# This is expected, so don't test for that.
if {[target_info gdb_protocol] == "remote"
|| [target_info gdb_protocol] == "extended-remote"} {
return
}