public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug server/17239] New: gdbserver errantly exits from rerun after failed previous run Date: Thu, 07 Aug 2014 18:10:00 -0000 [thread overview] Message-ID: <bug-17239-4717@http.sourceware.org/bugzilla/> (raw) 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.
reply other threads:[~2014-08-07 18:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-17239-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).