[Bug gdb/22841] Executable gets not downloaded with remote-stdio-gdbserver.exp board

["c.schwarzgruber.cs at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=22841

--- Comment #13 from Christian <c.schwarzgruber.cs at gmail dot com> ---
Created attachment 10871
  --> https://sourceware.org/bugzilla/attachment.cgi?id=10871&action=edit
Fix remote file not deleted

Here is a bit more verbose output of the command "runtest -v -v -v
--target_board=remote-stdio-gdbserver REMOTE_USERNAME=root
REMOTE_HOSTNAME=192.168.31.7 REMOTE_TMPDIR=/tmp".

Before the patch.


call_remote  file remote-stdio-gdbserver delete /tmp/arm-bl-branch-dest         
board_info remote-stdio-gdbserver file_transfer                                 
getting remote-stdio-gdbserver file_transfer                                    
board_info remote-stdio-gdbserver connect                                       
getting remote-stdio-gdbserver connect                                          
call_remote calling remote-stdio-gdbserver_file                                 
board_info target name                                                          
getting remote-stdio-gdbserver name                                             
board_info remote-stdio-gdbserver exists username                               
board_info target name                                                          
getting remote-stdio-gdbserver name                                             
board_info remote-stdio-gdbserver username                                      
getting remote-stdio-gdbserver username                                         
board_info target name                                                          
getting remote-stdio-gdbserver name                                             
board_info remote-stdio-gdbserver exists hostname                               
board_info target name                                                          
getting remote-stdio-gdbserver name                                             
board_info remote-stdio-gdbserver hostname                                      
getting remote-stdio-gdbserver hostname                                         
Executing on root@192.168.31.7: rm -f /tmp/arm-bl-branch-dest    (timeout =
300)                        
calling is_remote root@192.168.31.7                                             
board_info build name                                                           
getting dev-pc name                                                             
board_info host name                                                            
getting dev-pc name                                                             
board_info root@192.168.31.7 exists isremote                                    
board_info root@192.168.31.7 exists remotedir                                   
board_info root@192.168.31.7 exists name
board_info root@192.168.31.7 exists name
dirlist is
/home/dev/workspaces/buildroot/buildroot/buildroot/output/build/host-gdb-8.1/gdb/testsuite/boards/../boards
/usr/share/dejagnu/baseboards
hostname=dev-pc
Looking for standard board description file 
/home/dev/workspaces/buildroot/buildroot/buildroot/output/build/host-gdb-8.1/gdb/testsuite/boards/../boards/standard.exp
Looking for standard board description file 
/usr/share/dejagnu/baseboards/standard.exp
Looking for board description file 
/home/dev/workspaces/buildroot/buildroot/buildroot/output/build/host-gdb-8.1/gdb/testsuite/boards/../boards/root@192.168.31.7.exp
Looking for board description file 
/usr/share/dejagnu/baseboards/root@192.168.31.7.exp
board_info root@192.168.31.7 exists protocol
board_info root@192.168.31.7 generic_name
getting root@192.168.31.7 generic_name
call_remote  exec root@192.168.31.7 {rm -f /tmp/arm-bl-branch-dest} {} {} {}
board_info root@192.168.31.7 file_transfer
getting root@192.168.31.7 file_transfer
board_info root@192.168.31.7 connect
getting root@192.168.31.7 connect
call_remote calling standard_exec
Executing on root@192.168.31.7: rm -f /tmp/arm-bl-branch-dest  <
board_info root@192.168.31.7 exists rsh_prog
Checking /usr/local/sbin for remsh
Checking /usr/local/bin for remsh
Checking /usr/bin for remsh
Checking /usr/lib/jvm/default/bin for remsh
Checking /usr/bin/site_perl for remsh
Checking /usr/bin/vendor_perl for remsh
Checking /usr/bin/core_perl for remsh
Checking /opt/loytec/toolchains/arm-at91sama5d3-linux/1.6/usr/bin for remsh
Checking /home/dev/.local/bin for remsh
Checking /home/dev/Developing/Scripts/enabled for remsh
board_info root@192.168.31.7 exists username
board_info root@192.168.31.7 exists name
board_info root@192.168.31.7 name
getting root@192.168.31.7 name
board_info root@192.168.31.7 exists hostname
spawn [open ...]
pid is 4327 4328 -4327 -4328
192.168.31.7: Connection refused
pid is -1
close result is child process exited abnormally
output is 192.168.31.7: Connection refused
 status 1
rsh status is 1, output is 192.168.31.7: Connection refused


And this is the output after the patch. The file gets now properly deleted on
the remote site.

call_remote  file remote-stdio-gdbserver delete /tmp/arm-bl-branch-dest         
board_info remote-stdio-gdbserver file_transfer                                 
getting remote-stdio-gdbserver file_transfer                                    
board_info remote-stdio-gdbserver connect                                       
getting remote-stdio-gdbserver connect                                         
                        call_remote calling remote-stdio-gdbserver_file
Executing on target: rm -f /tmp/arm-bl-branch-dest    (timeout = 300)
calling is_remote target
board_info build name
getting dev-pc name
board_info host name
getting dev-pc name
calling is_remote remote-stdio-gdbserver
board_info build name
getting dev-pc name
board_info host name
getting dev-pc name
board_info remote-stdio-gdbserver exists isremote
board_info remote-stdio-gdbserver isremote
getting remote-stdio-gdbserver isremote
board is remote-stdio-gdbserver, isremote is 1
board_info remote-stdio-gdbserver isremote
getting remote-stdio-gdbserver isremote
board_info target exists remotedir
board_info target remotedir
getting remote-stdio-gdbserver remotedir
board_info target exists name
board_info target name
getting remote-stdio-gdbserver name
board_info remote-stdio-gdbserver exists name
board_info remote-stdio-gdbserver exists protocol
board_info remote-stdio-gdbserver generic_name
getting remote-stdio-gdbserver generic_name
call_remote  exec remote-stdio-gdbserver {test -d /tmp && cd /tmp; rm -f
/tmp/arm-bl-branch-dest} {} {} {}
board_info remote-stdio-gdbserver file_transfer
getting remote-stdio-gdbserver file_transfer
board_info remote-stdio-gdbserver connect
getting remote-stdio-gdbserver connect
call_remote calling standard_exec
Executing on remote-stdio-gdbserver: test -d /tmp && cd /tmp; rm -f
/tmp/arm-bl-branch-dest  <
board_info remote-stdio-gdbserver exists rsh_prog
board_info remote-stdio-gdbserver rsh_prog
getting remote-stdio-gdbserver rsh_prog
board_info remote-stdio-gdbserver exists username
board_info remote-stdio-gdbserver username
getting remote-stdio-gdbserver username
board_info remote-stdio-gdbserver exists name
board_info remote-stdio-gdbserver name
getting remote-stdio-gdbserver name
board_info remote-stdio-gdbserver exists hostname
board_info remote-stdio-gdbserver hostname
getting remote-stdio-gdbserver hostname
spawn [open ...]
pid is 14886 14887 -14886 -14887
XYZ0ZYX
pid is -1
output is XYZ0ZYX
 status 0
/usr/bin/ssh status is 0, output is XYZ0ZYX


This is likely not the way to go, isn't it?

Christian

-- 
You are receiving this mail because:
You are on the CC list for the bug.