From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16419 invoked by alias); 3 Mar 2005 14:34:04 -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 16370 invoked from network); 3 Mar 2005 14:33:57 -0000 Received: from unknown (HELO lakermmtao02.cox.net) (68.230.240.37) by sourceware.org with SMTP; 3 Mar 2005 14:33:57 -0000 Received: from white ([68.9.64.121]) by lakermmtao02.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050303143352.JXBI867.lakermmtao02.cox.net@white>; Thu, 3 Mar 2005 09:33:52 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1D6rOk-0008Vm-00; Thu, 03 Mar 2005 09:33:54 -0500 Date: Thu, 03 Mar 2005 14:34:00 -0000 From: Bob Rossi To: Karganov Konstantin Cc: gdb@sources.redhat.com Subject: Re: Broken MI output Message-ID: <20050303143354.GB32613@white> Mail-Followup-To: Karganov Konstantin , gdb@sources.redhat.com References: <20050303142032.GA32613@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-SW-Source: 2005-03/txt/msg00023.txt.bz2 On Thu, Mar 03, 2005 at 05:20:51PM +0300, Karganov Konstantin wrote: > On Thu, 3 Mar 2005, Bob Rossi wrote: > > > The echoing should be turned off from the GDB side. There are several > > ways to do this. > The echoing doesn't matter since it does't go from gdb stdout. > > > Are you communicating with GDB through a pipe, pty? > Currently - through the pipe. > > > The inferior output needs to be redirected to another pty using the > > console 'tty' command. This will "unmix" the inferior output and the MI > > output. > And if I don't want to redirect it to pty (or even can't)? > There is a special grammar rule (target-stream-output) for this case but > it is not used! Why?.. I've never dealt with that, but I assume it's when GDB is talking to a target program, not a normal program on the host. A target program most likely has a special form of I/O, which is redirected through GDB. A program running on the host outputs directly to the terminal, and it's impossible for GDB to know anything about it. Unless of course, GDB puts a pty between the inferior and itself. Thanks, Bob Rossi