aboutsummaryrefslogtreecommitdiff
path: root/gprof
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2023-03-17 19:25:18 +0100
committerTom de Vries <tdevries@suse.de>2023-03-17 19:25:18 +0100
commit2a7d1e5ebbab35a6f3ff164653dfd0ba0e4448c0 (patch)
tree7f688e5fa951c1be0199c19762e56fe0398d30e3 /gprof
parent3741934fdb04cde6661335e160249f9a83e498a7 (diff)
downloadgdb-2a7d1e5ebbab35a6f3ff164653dfd0ba0e4448c0.zip
gdb-2a7d1e5ebbab35a6f3ff164653dfd0ba0e4448c0.tar.gz
gdb-2a7d1e5ebbab35a6f3ff164653dfd0ba0e4448c0.tar.bz2
[gdb/testsuite] Handle REMOTE_HOST_USERNAME in local-remote-host
Handle REMOTE_HOST_USERNAME in local-remote-host, similar to how that's done for REMOTE_TARGET_USERNAME in remote-gdbserver-on-localhost. This helps to keep the home dir clean. Since the setup makes $build/gdb/testsuite on build unreadable for the remote host, we run into permission problems for GDB and the data-directory, so fix this (as was done for gdbserver in gdbserver-base.exp) using file normalize. Tested on x86_64-linux.
Diffstat (limited to 'gprof')
0 files changed, 0 insertions, 0 deletions