aboutsummaryrefslogtreecommitdiff
path: root/COPYING3.LIB
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-04-24 15:36:02 +0200
committerTom de Vries <tdevries@suse.de>2024-04-24 15:36:02 +0200
commita47141329c8e984de61ba3c2f2394bcf4328ee92 (patch)
tree7f723e838caa6bbe9f872c5a34dfe98cbb3c4481 /COPYING3.LIB
parente6a0a281a0bf93bd22247bcd1d68b303dc657845 (diff)
downloadgdb-a47141329c8e984de61ba3c2f2394bcf4328ee92.zip
gdb-a47141329c8e984de61ba3c2f2394bcf4328ee92.tar.gz
gdb-a47141329c8e984de61ba3c2f2394bcf4328ee92.tar.bz2
[gdb/testsuite] Fix gdb.threads/threadcrash.exp for remote host
With test-case gdb.threads/threadcrash.exp using host board local-remote-host and target board remote-gdbserver-on-localhost I run into: ... (gdb) PASS: gdb.threads/threadcrash.exp: test_gcore: continue to crash gcore $outputs/gdb.threads/threadcrash/threadcrash.gcore^M Failed to open '$outputs/gdb.threads/threadcrash/threadcrash.gcore' for output.^M (gdb) FAIL: gdb.threads/threadcrash.exp: test_gcore: saving gcore UNSUPPORTED: gdb.threads/threadcrash.exp: test_gcore: couldn't generate gcore file ... The problem is that the gcore command tries to save a file on a remote host, but the filename is a location on build. Fix this by using host_standard_output_file. Tested on x86_64-linux.
Diffstat (limited to 'COPYING3.LIB')
0 files changed, 0 insertions, 0 deletions