Bug 17239 - gdbserver errantly exits from rerun after failed previous run
Summary: gdbserver errantly exits from rerun after failed previous run
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: server (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-07 18:10 UTC by dje
Modified: 2014-08-07 18:10 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dje 2014-08-07 18:10:48 UTC
bash1$ ./gdbserver --multi :1234
Listening on port 1234
Remote debugging from host 127.0.0.1
Process /home/dje/hello.x64  created; pid = 16578
Cannot exec /home/dje/hello.x64 : No such file or directory.

Child exited with status 127
Process /home/dje/hello.x64 created; pid = 16628
gdbserver: no target description
bash1$ 


bash2$ make run
(gdb) tar ext :1234
(gdb) file ~/hello
(gdb) set remote exec-file /home/dje/hello<space>
(gdb) start
Temporary breakpoint 1 at 0x4006d8: file hello.cc, line 6.
Starting program: /home/dje/hello
Running "/home/dje/hello " on the remote target failed
(gdb) set remote exec-file /home/dje/hello
(gdb) start
Temporary breakpoint 2 at 0x4006d8: file hello.cc, line 6.
Starting program: /home/dje/hello
Remote connection closed
(gdb)