diff options
| author | Pedro Alves <palves@redhat.com> | 2015-02-04 14:53:24 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-02-04 14:53:24 +0100 |
| commit | 42d9e5288b6576b56f3f803901433b88ee863bc6 (patch) | |
| tree | bace26533b18a08d1e4b07d2a8ae3b73b92165e7 /gold | |
| parent | f962539ad23759af4ba8f7eece1946fdc2f50876 (diff) | |
| download | gdb-42d9e5288b6576b56f3f803901433b88ee863bc6.zip gdb-42d9e5288b6576b56f3f803901433b88ee863bc6.tar.gz gdb-42d9e5288b6576b56f3f803901433b88ee863bc6.tar.bz2 | |
Fix '--target_board=native-extended-gdbserver/-m32'
Running the testsuite with the native-extended-gdbserver.exp board and
passing a variant spec, like
make check RUNTESTFLAGS="--target_board=native-extended-gdbserver/-m32"
results in dejagnu trying to open a rsh connection to
"native-extended-gdbserver", which of course is wrong. The point of
this board is running things locally.
The issue is that the native-extended-gdbserver board does not clear
the "isremote" flag properly.
Reported by Sergio at:
https://sourceware.org/ml/gdb-patches/2015-02/msg00067.html
testsuite/
2015-02-04 Pedro Alves <palves@redhat.com>
* boards/native-extended-gdbserver.exp: Remove any target variant
specifications from the board name before clearing the isremote
flag from board_info.
Diffstat (limited to 'gold')
0 files changed, 0 insertions, 0 deletions