From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] printf (stderr,... ->fprintf_unfiltered (gdb_stderr,... in remote*.c
Date: Thu, 25 Apr 2002 09:36:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020425183344.020b9a18@ics.u-strasbg.fr> (raw)
In-Reply-To: <3CC825CF.4090805@cygnus.com>
At 17:50 25/04/2002 , Andrew Cagney a écrit:
>>This is one of the files that I listed in
>>http://sources.redhat.com/ml/gdb/2002-02/msg00212.html
>>as still having direct uses of stderr.
>> I don't even know if this is correct,
>>because I don't know if the gdb_std???
>>should be used in these files.
>
>It should be used everywhere, so yes it is fine.
>
>>remote-array.c seems to also use gdb_stdout
>>so that one should be correct.
>
>Yes.
>
>(Eventually GDB needs to audit all its error/output messages and decide which should go where. That, however, is a separate problem. Probably something to do if/when i18n occures.)
>
>>remote-es.c has no other reference to gdb_std???
>>variables, so here it could well be an error to do that change.
>>Idem for remote-os9k.c and remote-st.c.
>
>These can also also be changed. gdb_stderr is defined in defs.h, so it is visible.
Can I commit the whole together then?
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
next prev parent reply other threads:[~2002-04-25 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 6:32 Pierre Muller
2002-04-25 8:50 ` Andrew Cagney
2002-04-25 9:36 ` Pierre Muller [this message]
2002-04-25 10:17 ` Andrew Cagney
2002-04-26 1:56 ` [RFA 2nd] remote-*.c printf (stderr,... ->fprintf_unfiltered (gdb_stderr, Pierre Muller
2002-04-26 6:12 ` Andrew Cagney
2002-04-29 4:02 ` Pierre Muller
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=4.2.0.58.20020425183344.020b9a18@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=ac131313@cygnus.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