From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28918 invoked by alias); 1 Dec 2005 14:32:29 -0000 Received: (qmail 28911 invoked by uid 22791); 1 Dec 2005 14:32:28 -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.1) with ESMTP; Thu, 01 Dec 2005 14:32:24 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EhpTu-0003R4-9D; Thu, 01 Dec 2005 09:32:18 -0500 Date: Thu, 01 Dec 2005 14:32:00 -0000 From: Daniel Jacobowitz To: Denis PILAT , Nick Roberts , gdb-patches@sources.redhat.com Subject: Re: [PATCH] Target stderr not displayed thru MI Message-ID: <20051201143218.GB13069@nevyn.them.org> Mail-Followup-To: Denis PILAT , Nick Roberts , gdb-patches@sources.redhat.com References: <17293.36697.854192.691800@kahikatea.snap.net.nz> <438DA1DE.2020406@st.com> <17294.2894.345752.773239@kahikatea.snap.net.nz> <438F011F.7050403@st.com> <20051201140436.GA31759@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051201140436.GA31759@white> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00014.txt.bz2 On Thu, Dec 01, 2005 at 09:04:36AM -0500, Bob Rossi wrote: > > I attach a new patch in that sense. It does not include the documentation > > patch about MI new stream but it's just to give you an idea. > > Any comment ? > > > + /* MI 1 and 2 target error stream use the same steam prefix "@" in oder > > + to ensure backward compatibility with old frondtend, MI 3 uses > > + a new prefix "#" */ > > + if (mi_version (uiout) > 2) > > + mi->targerr = mi_console_file_new (raw_stdout, "#", '"'); > > + else > > + mi->targerr = mi_console_file_new (raw_stdout, "@", '"'); > > + > > mi->event_channel = mi_console_file_new (raw_stdout, "=", 0); > > We have a lot of people that are confused about the target-stream-output > and it was recently brought up that maybe this wasn't used and should be > removed. > > http://sources.redhat.com/ml/gdb/2005-11/msg00391.html > > However, you seem to be using it, and want to add another stream-output, > probably called something like target-stream-stderr-output. > > I haven't seen MI use the target-stream-output yet. What is your > configuration that makes this happen? Is it still useful to you? > If so, it would be nice if we could improve the doco a bit, to let users > know when this would be useful for them. It's used for any (most?) remote or simulator targets that can provide output. I'm sorry if I was not adequately clear about that. The ST folks appear to have their own proprietary remote target, which also generates these packets. Nick, what's your reasoning for separating this from the stdout data? When we put the inferior onto its own TTY, we don't get stdout and stderr separated, either. -- Daniel Jacobowitz CodeSourcery, LLC