Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Vladimir Prus'" <vladimir@codesourcery.com>
Cc: <tromey@redhat.com>,
	"'Thiago Jung Bauermann'" <bauerman@br.ibm.com>,
	        <gdb-patches@sourceware.org>
Subject: RE: TR: ARI warning list change Fri May 29 01:53:26 UTC 2009
Date: Fri, 29 May 2009 09:43:00 -0000	[thread overview]
Message-ID: <000901c9e041$c517b0d0$4f471270$@u-strasbg.fr> (raw)
In-Reply-To: <200905291309.11553.vladimir@codesourcery.com>

Sorry,

The ARI stands for Awk Regression index
and is a script (named gdb_ari.sh) that is run once a day by
the machine on which the webite is.

The result of this script is transformed into a web page:
http://sourceware.org/gdb/current/ari/

Most used files are accessible at the bottom of the web page,
in particular gdb_ari.sh is at:
http://sourceware.org/gdb/current/ari/gdb_ari.sh


A recent change I made adds a email generation that is
only sent to me until now, but I was trying to
get this sent to gdb-testers.
The email message can be seen of the website:
http://sourceware.org/gdb/current/ari/mail-message

This message shows the differences between
yesterday's and today's list of warnings generated by gdb_ari.sh.


The email that I got this night was
>>>>>>>>>>Current version of email message
657a658,659
> gdb/mi/mi-cmd-var.c:251: gettext: _ markup: All messages should be marked
up with _.
> gdb/mi/mi-cmd-var.c:256: gettext: _ markup: All messages should be marked
up with _.
837a840,846
> gdb/varobj.c:853: gettext: _ markup: All messages should be marked up with
_.
> gdb/varobj.c:859: gettext: _ markup: All messages should be marked up with
_.
> gdb/varobj.c:865: gettext: _ markup: All messages should be marked up with
_.
> gdb/varobj.c:882: gettext: _ markup: All messages should be marked up with
_.
> gdb/varobj.c:1386: gettext: _ markup: All messages should be marked up
with _.
> gdb/varobj.c:1457: gettext: _ markup: All messages should be marked up
with _.
> gdb/varobj.c:1470: gettext: _ markup: All messages should be marked up
with _.
1204d1212
< gdb/value.c:529: deprecated: deprecated value_address_hack: Do not use
deprecated value_address_hack, see declaration for details
1395,1396d1402
< gdb/value.h:278: deprecated: deprecated value_address_hack: Do not use
deprecated value_address_hack, see declaration for details
< gdb/value.h:279: deprecated: deprecated value_address_hack: Do not use
deprecated value_address_hack, see declaration for details
>>>>>>>>>>End of current version of email message

This shows that your patch generated new warnings,
but also removed three warnings about the deprecated use of
value_address_hack
that is completely removed. This is great.

  But it also lists several positions,
with file source and line number of
additional warnings. For that patch all new warnings
are of the same kind. This is one of the rules checked
by gdb_ari.sh that verifies that all constant messages
are enclosed in _() markers for internalization.

  As you pointed out, the mi code might be unsuitable
for these markers, but I suppose that for the gdb/varobj.c

  A newer version of update-web-ari (that I didn't commit yet)
improves the email by also listing the corresponding source line:
>>>>>>>>>>New version of email message
941a942,943
> gdb/mi/mi-cmd-var.c:251: gettext: _ markup: All messages should be marked
up with _.
gdb/mi/mi-cmd-var.c:251:    error ("Usage: NAME VISUALIZER_FUNCTION.");
> gdb/mi/mi-cmd-var.c:256: gettext: _ markup: All messages should be marked
up with _.
gdb/mi/mi-cmd-var.c:256:    error ("Variable object not found");
1724d1725
< gdb/value.c:529: deprecated: deprecated value_address_hack: Do not use
deprecated value_address_hack, see declaration for details
gdb/value.c:529:deprecated_value_address_hack (struct value *value)
1735,1736d1735
< gdb/value.h:278: deprecated: deprecated value_address_hack: Do not use
deprecated value_address_hack, see declaration for details
gdb/value.h:278:extern CORE_ADDR *deprecated_value_address_hack (struct
value *);
< gdb/value.h:279: deprecated: deprecated value_address_hack: Do not use
deprecated value_address_hack, see declaration for details
gdb/value.h:279:#define VALUE_ADDRESS(val) (*deprecated_value_address_hack
(val))
1742a1742,1748
> gdb/varobj.c:853: gettext: _ markup: All messages should be marked up with
_.
gdb/varobj.c:853:      error ("Null value returned for children");
> gdb/varobj.c:859: gettext: _ markup: All messages should be marked up with
_.
gdb/varobj.c:859:    error ("Returned value is not iterable");
> gdb/varobj.c:865: gettext: _ markup: All messages should be marked up with
_.
gdb/varobj.c:865:      error ("Could not get children iterator");
> gdb/varobj.c:882: gettext: _ markup: All messages should be marked up with
_.
gdb/varobj.c:882:	error ("Invalid item from the child list");
> gdb/varobj.c:1386: gettext: _ markup: All messages should be marked up
with _.
gdb/varobj.c:1386:  error ("Python support required");
> gdb/varobj.c:1457: gettext: _ markup: All messages should be marked up
with _.
gdb/varobj.c:1457:      error ("Could not evaluate visualizer expression:
%s", visualizer);
> gdb/varobj.c:1470: gettext: _ markup: All messages should be marked up
with _.
gdb/varobj.c:1470:  error ("Python support required");
>>>>>>>>>>End of new version of email message 
  
  By looking at this I tend to think that these messages
should indeed be translated if we ever translate gdb...

 I hope this explains a little bit what ARI is all about.

Pierre


  reply	other threads:[~2009-05-29  9:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29  6:52 Pierre Muller
2009-05-29  7:40 ` Vladimir Prus
2009-05-29  8:32   ` Pierre Muller
2009-05-29  9:09     ` Vladimir Prus
2009-05-29  9:43       ` Pierre Muller [this message]
2009-06-08  1:31         ` Thiago Jung Bauermann
2009-06-05 18:53 ` Tom Tromey
2009-06-05 19:43   ` Tom Tromey

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='000901c9e041$c517b0d0$4f471270$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    --cc=vladimir@codesourcery.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