aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/python.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2023-03-09 10:45:03 +0100
committerTom de Vries <tdevries@suse.de>2023-03-09 10:45:03 +0100
commit593dda1880146c1487828f2878d5e74c9b1b42ad (patch)
treeff04fee2fae08d2939da6fd318b0b39178bde3fc /gdb/python/python.c
parent6407713fab73abcfcf1893451bfc6ac6c91e609c (diff)
downloadbinutils-593dda1880146c1487828f2878d5e74c9b1b42ad.zip
binutils-593dda1880146c1487828f2878d5e74c9b1b42ad.tar.gz
binutils-593dda1880146c1487828f2878d5e74c9b1b42ad.tar.bz2
[gdb/testsuite] Fix gdbserver path in remote-stdio-gdbserver.exp
With test-case gdb.server/unittest.exp and target board remote-stdio-gdbserver I run into: ... (gdb) builtin_spawn /usr/bin/ssh -t -l vries localhost /usr/bin/gdbserver \ --selftest^M Selftests have been disabled for this build.^M UNSUPPORTED: gdb.server/unittest.exp: unit tests ... due to using the system gdbserver /usr/bin/gdbserver rather than the one from the build. Fix this by removing the hard-coding of /usr/bin/gdbserver in remote-stdio-gdbserver, allowing find_gdbserver to do its work, such that we have instead: ... (gdb) builtin_spawn /usr/bin/ssh -t -l vries localhost \ /data/vries/gdb/leap-15-4/build/gdbserver/gdbserver --selftest^M Running selftest remote_memory_tagging.^M Ran 1 unit tests, 0 failed^M Connection to localhost closed.^M^M PASS: gdb.server/unittest.exp: unit tests ... Tested on x86_64-linux.
Diffstat (limited to 'gdb/python/python.c')
0 files changed, 0 insertions, 0 deletions