From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9042 invoked by alias); 12 Dec 2004 15:25:53 -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 9001 invoked from network); 12 Dec 2004 15:25:50 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 12 Dec 2004 15:25:50 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iBCFPjHQ010079 for ; Sun, 12 Dec 2004 10:25:50 -0500 Received: from localhost.redhat.com (vpn50-50.rdu.redhat.com [172.16.50.50]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iBCFPir30751; Sun, 12 Dec 2004 10:25:45 -0500 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6EE6F3EF9; Sun, 12 Dec 2004 10:23:43 -0500 (EST) Message-ID: <41BC627C.2070702@gnu.org> Date: Sun, 12 Dec 2004 15:25:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: Johannes Overmann Cc: gdb@sources.redhat.com Subject: Re: Not seeing target output in GDB/MI References: <41B97648.5040107@arm.com> In-Reply-To: <41B97648.5040107@arm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00084.txt.bz2 > - Is there a way to see the target output (stdout) unbuffered or line > buffered > and still using pipes to comminucate with gdb? > > - Why is the target output not visible in the target-stream-output > described in the > MI documentation (e.g. prefixed by @)? I see it just as any other output > coming from gdb without any indication that it comes from the target. MI was first developed on a remote target where implementing this was relatively easy. That isn't the case for native and the code was never written. Instead, as you note for DDD, native MI clients use 'gdb --tty=...'. Perhaphs the thing to do here is deprecate the MI mechanism and recommend -tty for both native and remote cases (this of course will mean that the remotes need to be changed). Andrew