This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug server/17239] New: gdbserver errantly exits from rerun after failed previous run
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 07 Aug 2014 18:10:48 +0000
- Subject: [Bug server/17239] New: gdbserver errantly exits from rerun after failed previous run
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17239
Bug ID: 17239
Summary: gdbserver errantly exits from rerun after failed
previous run
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: server
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
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)
--
You are receiving this mail because:
You are on the CC list for the bug.