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/16879] New: support gdbserver with named pipes Date: Mon, 28 Apr 2014 17:38:00 -0000 [thread overview] Message-ID: <bug-16879-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16879 Bug ID: 16879 Summary: support gdbserver with named pipes Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: dje at google dot com IWBN to use gdbserver with named pipes. That can be done today using "stdio" as the "comm port" and redirecting stdio to/from the named pipes, except that if one is also using --multi and gdb goes away then gdbserver gets into an infinite loop trying to read stdin which returns EOF. gdbserver needs to close the port and reopen it, but that doesn't work too well for stdin (gdbserver doesn't know what to reopen as stdin, and the close and reopen are done in different parts of the code so there's no real guarantee that stdin won't have accidently been assigned to something else in between). A related PR is https://sourceware.org/bugzilla/show_bug.cgi?id=8637 but it concerns the gdb side. [btw, named pipes are unidirectional so "target remote /foo/named-pipe" is insufficient] This PR concerns the gdbserver side. gdb may be using, e.g., "target {extended-,}remote | ssh mumble" to connect to a previously started gdbserver that is using named pipes. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2014-04-28 17:38 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-16879-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).