From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1167 invoked by alias); 11 Jan 2002 01:30:17 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1009 invoked by uid 22784); 11 Jan 2002 01:30:12 -0000 From: Michael Snyder Newsgroups: cygnus.gdb Subject: Re: remote stdio Date: Thu, 10 Jan 2002 17:30:00 -0000 Organization: Red Hat, Inc. Message-ID: <3C3E3D84.52FEF644@redhat.com> References: <200201101827.NAA423637035@node128.ott.qnx.com> NNTP-Posting-Host: reddwarf.sfbay.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: cronkite.cygnus.com 1010712249 22914 205.180.231.12 (11 Jan 2002 01:24:09 GMT) X-Complaints-To: postmaster@cygnus.com NNTP-Posting-Date: 11 Jan 2002 01:24:09 GMT X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2smp i686) X-Accept-Language: en To: gdb@sources.redhat.com DJ-Gateway: from newsgroup cygnus.gdb X-SW-Source: 2002-01/txt/msg00114.txt.bz2 Graeme Peterson wrote: > > Hi, all. > > I have a remote stub working for QNX's remote debug server. > The server manages stdin, out and err, however I am having > trouble finding out how GDB shares the text console's stdin > for a remote target. It doesn't. The remote protocol has no provision for this. > When the inferior is given free reign to run, and GDB winds up > waiting for ever, what mechanisms exist to allow any subsequent > keyboard input to be captured and sent to the remote target? None. > Basically, I want to respond to a getch() in the inferior, or > run a 'vi' session in DDD's execution window via the remote > target connection. If you get it working, please submit it! ;-) > What I have done so far is added the stdin fd to the fd set > for the select() in ser_unix_wait_for (gdb/ser-unix.c). This > works fine for TCP/IP connections, but the code path is not > executed for serial connections. I would also prefer not > to modify the generic GDB source files if a mechanism exists > that I can take advantage of. Sorry, you are going to have to 1) Extend the remote protocol, and 2) extend gdb.