aboutsummaryrefslogtreecommitdiff
path: root/missing
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2023-03-15 16:38:03 +0100
committerTom de Vries <tdevries@suse.de>2023-03-15 16:38:03 +0100
commit81a7a72f67a318be7e1a4755ee83bafb40dcead2 (patch)
tree25e8a35800b0d5fc0edf26e65d957f9d7402fa87 /missing
parent2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b (diff)
downloadbinutils-81a7a72f67a318be7e1a4755ee83bafb40dcead2.zip
binutils-81a7a72f67a318be7e1a4755ee83bafb40dcead2.tar.gz
binutils-81a7a72f67a318be7e1a4755ee83bafb40dcead2.tar.bz2
[gdb/testsuite] Fix gdb.arch/amd64*.exp with local-remote-host-native.exp
There's a number of gdb.arch/amd64*.exp test-cases that fail with host+target board local-remote-host-native.exp because of using a .S file, generated from a .c file. If a test-case compiles the .S file when executing on remote host, the .S file is already copied from build to host, such that it's available for the compiler. But that's not the case for the .c file, which is needed by gdb to show a source line: ... (gdb) continue^M Continuing.^M ^M Breakpoint 2, fn2 (y=y@entry=25, x=x@entry=6) at amd64-entry-value-inline.c:32^M 32 in gdb.arch/amd64-entry-value-inline.c^M (gdb) FAIL: gdb.arch/amd64-entry-value-inline.exp: continue to breakpoint: \ break-here ... Fix this by using "gdb_remote_download host <.c file>". Tested on x86_64-linux, with host+target board local-remote-host-native.
Diffstat (limited to 'missing')
0 files changed, 0 insertions, 0 deletions