diff options
| author | Tom de Vries <tdevries@suse.de> | 2023-03-15 16:38:03 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2023-03-15 16:38:03 +0100 |
| commit | fdefd3b5314677eb838d28866d0fcf6cf6546222 (patch) | |
| tree | 8d1d8607c2852fe13377750380e91ac0d28909b5 /gdb/tic6x-linux-tdep.c | |
| parent | 7b0d27b62f51e0997407383100dbc64b7bc5f4ef (diff) | |
| download | binutils-fdefd3b5314677eb838d28866d0fcf6cf6546222.zip binutils-fdefd3b5314677eb838d28866d0fcf6cf6546222.tar.gz binutils-fdefd3b5314677eb838d28866d0fcf6cf6546222.tar.bz2 | |
[gdb/testsuite] Fix gdb.arch/amd64-stap-special-operands.exp for remote host
With test-case gdb.arch/amd64-stap-special-operands.exp and host board
local-remote-host-notty and target board native-gdbserver I run into:
...
(gdb) break -pstap three_arg^M
No probe matching objfile=`<any>', provider=`<any>', name=`three_arg'^M
Make breakpoint pending on future shared library load? (y or [n]) n^M
(gdb) FAIL: gdb.arch/amd64-stap-special-operands.exp: probe: three_arg: \
gdb_breakpoint: set breakpoint at -pstap three_arg
...
due to compiling two executables with the same name, and when uploading the
second one from host to build, we run into:
...
Upload from 127.0.0.1 failed, \
$outputs/gdb.arch/amd64-stap-special-operands/amd64-stap-special-operands: \
Text file busy.
...
Fix this by making the executable names unique.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/tic6x-linux-tdep.c')
0 files changed, 0 insertions, 0 deletions