From: Sergio Durigan Junior <sergiodj@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: New ARI warning Tue Feb 5 02:01:10 UTC 2013 in -D 2013-02-05-gmt
Date: Wed, 06 Feb 2013 02:05:00 -0000 [thread overview]
Message-ID: <m3k3qmnqns.fsf@redhat.com> (raw)
In-Reply-To: <20130205020110.GA5646@sourceware.org> (GDB Administrator's message of "Tue, 5 Feb 2013 02:01:10 +0000")
On Tuesday, February 05 2013, GDB Administrator wrote:
>> gdb/gdbarch.h:740: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
> gdb/gdbarch.h:740:/* The elfcore writer hook to use to write Linux prpsinfo notes to core
>> gdb/gdbarch.h:741: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
> gdb/gdbarch.h:741: files. Most Linux architectures use the same prpsinfo32 or
>> gdb/gdbarch.h:743: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
> gdb/gdbarch.h:743: call the Linux generic routines in bfd to write prpsinfo notes by
> 556a562
These were introduced by the PRPSINFO patches, but I don't agree with
them (and don't see an elegant way to fix them). Is there any way to
silent those warnings?
--
Sergio
next prev parent reply other threads:[~2013-02-06 2:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 2:01 GDB Administrator
2013-02-05 10:09 ` Pierre Muller
2013-02-14 9:44 ` [RFC/RFA] Remove ARI warning for set_gdbarch_write_pc use Pierre Muller
2013-04-15 17:33 ` Joel Brobecker
2013-02-06 2:05 ` Sergio Durigan Junior [this message]
2013-02-06 9:59 ` New ARI warning Tue Feb 5 02:01:10 UTC 2013 in -D 2013-02-05-gmt Pierre Muller
2013-02-06 10:04 ` [RFC] Remove ARI GNU/Linux rule (was: New ARI warning Tue Feb 5 02:01:10 UTC 2013 in -D 2013-02-05-gmt) Pierre Muller
2013-02-06 15:29 ` Joel Brobecker
2013-02-14 13:56 ` Joel Brobecker
2013-02-14 21:09 ` Pierre Muller
[not found] ` <19773.0148713619$1360145095@news.gmane.org>
2013-02-06 16:08 ` [RFC] Remove ARI GNU/Linux rule Tom Tromey
[not found] ` <002001ce0450$9de57b00$d9b07100$%muller@ics-cnrs.unistra.fr>
[not found] ` <002301ce0451$4cbc6440$e6352cc0$%muller@ics-cnrs.unistra.fr>
2013-02-06 18:26 ` [RFC] Remove ARI GNU/Linux rule (was: New ARI warning Tue Feb 5 02:01:10 UTC 2013 in -D 2013-02-05-gmt) Eli Zaretskii
2013-02-06 19:19 ` Joel Brobecker
2013-02-06 19:39 ` Eli Zaretskii
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=m3k3qmnqns.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
/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