RE: New ARI warning Tue Feb 5 02:01:10 UTC 2013 in -D 2013-02-05-gmt

Pierre Muller
2013-02-06T09:59:39Z

This issue has been discussed partly
already in the thread:

http://sourceware.org/ml/gdb-patches/2009-04/msg00286.html

But I don't think that we really reached the point
to agree that we should simply completely remove this
rule.

I will resubmit the removal as a separate email
to see if we can agree on it.

Pierre
as ARI maintainer

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Sergio Durigan Junior
> Envoyé : mercredi 6 février 2013 03:05
> À : gdb-patches@sourceware.org
> Objet : Re: New ARI warning Tue Feb 5 02:01:10 UTC 2013 in -D
2013-02-05-gmt
>
> 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