Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pierre Muller <muller@ics.u-strasbg.fr>
To: Daniel Jacobowitz <drow@mvista.com>,
	Elena Zannoni <ezannoni@redhat.com>,
	Andrew Cagney <ac131313@redhat.com>
Cc: fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] cli-out.c new function
Date: Wed, 06 Nov 2002 01:08:00 -0000	[thread overview]
Message-ID: <5.0.2.1.2.20021106094824.02b66088@ics.u-strasbg.fr> (raw)
In-Reply-To: <20021106032636.GC16623@nevyn.them.org>

At 04:26 06/11/2002, Daniel Jacobowitz wrote:
>On Tue, Nov 05, 2002 at 06:22:37PM -0500, Elena Zannoni wrote:
>> 
>> This function sets the stream of the uiout file to the given
>> parameter.  It is used in the interpreter work. Maybe Keith or JimI
>> can explain this a bit better, but switching interpreters can change
>> the gdb_sdout.
>> 
>> 
>>   /* gdb_stdout could change between the time cli_uiout was initialized
>>      and now. Since we're probably using a different interpreter which has
>>      a new ui_file for gdb_stdout, use that one instead of the default.
>> 
>>      It is important that it gets reset everytime, since the user could
>>      set gdb to use a different interpreter. */
>>   old_stream = cli_out_set_stream (cli_uiout, gdb_stdout);
>
>Something (two things actually) very much like this were discussed and
>we never reached agreement on them.  See my patch for a `tee' command
>and file redirection; and something similar from Pierre.  A couple of
>months ago now.

See the following threads:
[RFC/RFA] avoid spurious Watchpoint X output on cygwin native target.
http://sources.redhat.com/ml/gdb-patches/2002-07/msg00323.html

and
RFA: Make cli-out follow gdb_stdout
http://sources.redhat.com/ml/gdb-patches/2002-07/msg00366.html
as well as
(which is a different thread, probably because I didn't use Relpy...)
http://sources.redhat.com/ml/gdb-patches/2002-08/msg00549.html

But honestly, I don't know if the this new function solves the
problem...
IMHO, standard gdb sources should not have to worry at all about
the possible fact that an interpreter is present...
The fact that standard gdb code redirects gdb_stdout (or gdb_stderr)
should be respected by any interpreter, no?
Thus I still think that the best solution is the double pointer one...
but Andrew is stronly opposed to that solution....


Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99


  reply	other threads:[~2002-11-06  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 15:26 Elena Zannoni
2002-11-05 19:25 ` Daniel Jacobowitz
2002-11-06  1:08   ` Pierre Muller [this message]
2002-11-06 10:16     ` Elena Zannoni
2002-11-06 11:16       ` Elena Zannoni
2002-11-05 23:00 ` Eli Zaretskii
2002-11-06 11:26   ` Elena Zannoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.0.2.1.2.20021106094824.02b66088@ics.u-strasbg.fr \
    --to=muller@ics.u-strasbg.fr \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=ezannoni@redhat.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox