From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28138 invoked by alias); 26 Feb 2003 21:19:41 -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 28131 invoked from network); 26 Feb 2003 21:19:40 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 26 Feb 2003 21:19:40 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id AF4C22A9C; Wed, 26 Feb 2003 16:21:56 -0500 (EST) Message-ID: <3E5D2FF4.1040108@redhat.com> Date: Wed, 26 Feb 2003 21:19:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb@sources.redhat.com Subject: Re: [RFC] File-I/O, target access to host file system via gdb remote protocol enhancement References: <20021111131354.N10395@cygbert.vinschen.de> <20021112212526.GA28814@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00574.txt.bz2 > > I like this one too; but I'm not sure that I like linking it to the > remote-syscall interface. Implementation-wise, that's the most useful > method for a stub like RedBoot; but for a larger system like gdbserver, > it's useful to allocate the program a normal pseudo-terminal as if it > had a console. And to do character rather than line I/O. > > As I'm sure Andrew will remind me, my suggestion doesn't fit the > current remote protocol very well; it's not synchronous enough for one > thing. So don't take this as an objection, and I'll come back to > proper remote console support a little later. This'll be a nice > starting point. Just FYI. The protocol doesn't preclude doing character IO and doesn't preclude the remote end using a pty. The pty problem is that it is more complex. The debug agent (or GDB, in the case of the MI console) needs to be able to juggle events from multiple sources (wait and i/o). Anyway, if the overhead of character i/o proves to be too great then a refinement can be made. Andrew