From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18694 invoked by alias); 28 Apr 2014 17:38:59 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 18664 invoked by uid 48); 28 Apr 2014 17:38:58 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug server/16879] New: support gdbserver with named pipes Date: Mon, 28 Apr 2014 17:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: dje at google dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q2/txt/msg00136.txt.bz2 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.