Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

[gdb/testsuite] Fix gdb.arch/amd64-stap-special-operands.exp for remote host

Browse Source 
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.
This commit is contained in:
Tom de Vries
2023-03-15 16:38:03 +01:00
parent 7b0d27b62f
commit fdefd3b531
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/gdb.arch/amd64-stap-special-operands.exp
View File

@@ -28,7 +28,7 @@ proc test_probe { probe_name } {
standard_testfile amd64-stap-triplet.S
if { [prepare_for_testing "failed to prepare" $testfile $srcfile] } {
if { [prepare_for_testing "failed to prepare" $testfile-triplet $srcfile] } {
return -1
}
@@ -36,7 +36,8 @@ test_probe "triplet"
standard_testfile amd64-stap-three-arg-disp.S
if { [prepare_for_testing "failed to prepare" $testfile $srcfile] } {
if { [prepare_for_testing "failed to prepare" $testfile-three-arg-displ \
$srcfile] } {
return -1
}