Tighten remote check in gdb.base/argv0-symlink.exp
authorPedro Alves <palves@redhat.com>
Thu, 12 Oct 2017 18:16:47 +0000 (19:16 +0100)
committerPedro Alves <palves@redhat.com>
Thu, 12 Oct 2017 18:16:54 +0000 (19:16 +0100)
commit30440677f3d0cdd2085bea40496774ffa24f6bb1
tree06e8eb42e9c20482863a6b91dd844f4df250ee79
parent4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f
Tighten remote check in gdb.base/argv0-symlink.exp

Check for gdbserver instead of dejagnu remote.  Unlike what the
comment says, the test actually fails with target remote + gdbserver
(it does pass with extended-remote).  The result is:

 FAIL -> KFAIL with --target_board=native-gdbserver
 KPASS -> PASS with --target_board=native-extended-gdbserver

gdb/testsuite/ChangeLog:
2017-10-12  Pedro Alves  <palves@redhat.com>
    Simon Marchi  <simon.marchi@polymtl.ca>

* gdb.base/argv0-symlink.exp: kfail on remote gdbserver,
instead of on dejagnu remote boards.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/argv0-symlink.exp
This page took 0.038093 seconds and 4 git commands to generate.