Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>
Subject: Explanation: New ARI warning Wed Apr 21 01:54:25 UTC 2010
Date: Wed, 21 Apr 2010 07:40:00 -0000	[thread overview]
Message-ID: <001801cae125$cac33230$60499690$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20100421015425.GA10145@sourceware.org>

  Just to explain this email again:

  This is an automatic email generated by the 
script update-web-ari that regenerates every night the ARI page.
http://sourceware.org/gdb/current/ari/

  Recently, 
http://sourceware.org/ml/gdb-patches/2010-04/msg00149.html
Tom agreed that we should try to
send these email to gdb-patches directly.
  I committed this change to update-web-ari 
in revision 1.148 date 2010/04/08.
  Since that date, this is the first email.

  Let me try to explain its content.
> Objet : New ARI warning Wed Apr 21 01:54:25 UTC 2010
  This title indicates that the script believes
that a recent change to either ARI handling in the ss directory
or in the sources of GDB repository generated
an additional ARI warning.
  Reminder: ARI stands for Awk Regression Index
The name is probably due to the fact that it is mainly a
awk language script meant to list a series
of problems in the GDB sources.
See the link above.

> 266,267d265
> < gdb/defs.h:119: code: long long: Do not use 'long long', instead use
> LONGEST
> gdb/defs.h:119:#define LONGEST long long
> < gdb/defs.h:120: code: long long: Do not use 'long long', instead use
> LONGEST
> gdb/defs.h:120:#define ULONGEST unsigned long long

  These two lines by themselves would not have generated an
email to gdb-patches, because these correspond to two warnings
that disappeared.
  The reason of this is that I change gdb_ari.sh yesterday.
----------------------------
revision 1.102
date: 2010/04/20 09:39:21;  author: muller;  state: Exp;  lines: +2 -0
* Allow two "long long" in defs.h
----------------------------
  This is because defs.h has two
occurrences of "long long" that are necessary,
and as such should not generate a warning.


> 1072a1071
> > gdb/procfs.c:4090: code: sprintf: Do not use sprintf, instead use
> xstrprintf
> gdb/procfs.c:4090:      sprintf (name, ', pi->pid, map->pr_mapname);
> 1100d1098
> < gdb/procfs.c:5659: code: sprintf: Do not use sprintf, instead use
> xstrprintf
> gdb/procfs.c:5659:      sprintf (name, ', pi->pid, map->pr_mapname);

  This is the part that triggered the email to gdb-patches
In the series of patches committed by Joel tonight,
he added some uses of sprint function, 
which is banned by those ARI rules.
 Note that today procfs.c has 25 uses of sprint
instead of 23 yesterday.

  With this new automated email generation,
people committing patches that increase the number of
ARI warnings will at least get some information about it.
  Any simple patch that removes those warnings
should probably be considered as obvious.

Pierre Muller
as ARI maintainer.



  reply	other threads:[~2010-04-21  7:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  1:54 GDB Administrator
2010-04-21  7:40 ` Pierre Muller [this message]
2010-04-21  8:01   ` Explanation: " Pierre Muller
2010-04-21 14:22     ` Joel Brobecker

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='001801cae125$cac33230$60499690$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=brobecker@adacore.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