From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20054 invoked by alias); 18 Nov 2005 15:31:10 -0000 Received: (qmail 20035 invoked by uid 22791); 18 Nov 2005 15:31:07 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 18 Nov 2005 15:31:07 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1Ed8Ce-0002Yj-9D; Fri, 18 Nov 2005 10:31:04 -0500 Date: Fri, 18 Nov 2005 15:31:00 -0000 From: Daniel Jacobowitz To: Vladimir Prus , gdb@sources.redhat.com Subject: Re: Output from target in MI mode Message-ID: <20051118153104.GD9100@nevyn.them.org> Mail-Followup-To: Vladimir Prus , gdb@sources.redhat.com References: <20051118134819.GA2255@white> <200511181743.48398.ghost@cs.msu.su> <20051118144715.GB2255@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051118144715.GB2255@white> User-Agent: Mutt/1.5.8i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00391.txt.bz2 On Fri, Nov 18, 2005 at 09:47:15AM -0500, Bob Rossi wrote: > On Fri, Nov 18, 2005 at 05:43:46PM +0300, Vladimir Prus wrote: > > Sure, that's what happening now. But that pty handling is a bit messy, since > > gdb already knows what output comes from inferior, it could just prepend it > > with some character. > > Actually, I don't think it does. GDB allows the inferior to run, and the > inferior's output get's directed directly to the terminal (I believe). That is correct. If GDB easily knew which was which, it would already be using the MI-formatted output. > > > The 'target' in teh above sentence I believe is refering to when GDB is > > > using a remote protocol to a specific piece of hardware. It's not > > > refering to the host. > > > > Ok, then it's not clear to me either. There's specific packet in remote > > protocol ("OXXXX") which allows to pass arbitrary text from remote side to > > gdb. Is this what's printed with "@". Or there some other messages from > > remote that are also printed with "@" prefix? > > I'm not sure. I've never seen output with the "@" before it. If you are > on the host, you will not get the "@" before the I/O from the inferior > process. Someone else might be able to give you more details on when > target I/O is done, if at all. Bob was right again; it's used for the remote console output packets and was never implemented for anything else. At this point I suspect it should be removed from the MI. -- Daniel Jacobowitz CodeSourcery, LLC