From: Daniel Jacobowitz <drow@mvista.com>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: gdb@sources.redhat.com
Subject: Re: [RFA] remove fprintf (stderr, ...) from dwarf2read.c
Date: Thu, 14 Feb 2002 06:41:00 -0000 [thread overview]
Message-ID: <20020214094146.A31811@nevyn.them.org> (raw)
In-Reply-To: <4.2.0.58.20020214123916.019a6840@ics.u-strasbg.fr>
On Thu, Feb 14, 2002 at 01:04:18PM +0100, Pierre Muller wrote:
> Probably the obvious rule could apply here,
> but since my last "obvious fix" was a total fiasco,
> I prefer to ask once again for permission here.
>
> There are several other files that use
> fprintf (stderr,...)
>
> Here is the complete list I found:
> arm-tdep.c
> f-lang.c
> hpread.c
> i386-stub.c
> m68k-stub.c
> remote-array.c
> remote-es.c
> remote-os9k.c
> remote-st.c
> stop-gdb.c
> symm-nat.c
> gdbserver/gdbreplay.c
> gdbserver/linux-low.c
> gdbserver/low-hppabsd.c
> gdbserver/low-lynx.c
> gdbserver/low-nbsd.c
> gdbserver/low-sim.c
> gdbserver/low-sparc.c
> gdbserver/low-sun3.c
> gdbserver/remote-utils.c
> gdbserver/server.c
> gdbserver/utils.c
> nindy-share/Onindy.c
> nindy-share/nindy.c
> nlm/gdbserve.c
> rdi-share/devsw.c
> rdi-share/etherdrv.c
> rdi-share/hsys.c
>
>
> Some of these files, like i386-stub.c and m68k-stub.c don't even use defs.h
> (which contains the declaration of fprintf_unfiltered)
> and thus should not be changed but for most others (at least at gdb dir level)
> should be changed, no ?
Some of those belong to GDB and some do not. gdbserver/* do not;
i386-stub.c and m68k-stub.c do not, I believe. Most of the others do,
but it's worth verifying - nlm/gdbserve.c looks suspicious, for
example.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-14 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 4:04 Pierre Muller
2002-02-14 6:41 ` Daniel Jacobowitz [this message]
2002-02-15 13:04 ` Jim Blandy
2002-02-15 23:20 ` 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=20020214094146.A31811@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=muller@cerbere.u-strasbg.fr \
/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