Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>,
	Simon Marchi <simon.marchi@polymtl.ca>
Cc: GDB Administrator <gdbadmin@sourceware.org>, gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Aug 8 01:55:57 UTC 2018
Date: Thu, 09 Aug 2018 14:46:00 -0000	[thread overview]
Message-ID: <a0a2c933-b695-0499-2990-7f70bb749ff2@redhat.com> (raw)
In-Reply-To: <20180809143249.GA2452@adacore.com>

On 08/09/2018 03:32 PM, Joel Brobecker wrote:
>>> gdb/dwarf-index-write.c:1625:	perror_with_name ("rename");
>>>> gdb/dwarf-index-write.c:1640: gettext: _ markup: All messages should
>>>> be marked up with _.
>>> gdb/dwarf-index-write.c:1640:	perror_with_name ("rename");
>>
>> I think these can be ignored, since these messages can't be translated.
> 
> Let's add an ARI marker to document this, and silence the ARI?
> Otherwise, someone looking at the ARI report for some easy things
> to improve might come upon this one and waste time figuring out
> that these cannot be translated. And also, it would prevent the
> report from containing too many false positive...

The way we've been quieting the ARI in these cases is this is the wrap
in extra parens, without the "_":

 $ grep perror * | grep "(("
 event-loop.c:   perror_with_name (("poll"));
 event-loop.c:       perror_with_name (("select"));
 fbsd-nat.c:    perror_with_name (("ptrace"));
 fbsd-nat.c:    perror_with_name (("ptrace"));
 fbsd-nat.c:    perror_with_name (("ptrace"));
 ....

Thanks,
Pedro Alves


  reply	other threads:[~2018-08-09 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08  1:56 GDB Administrator
2018-08-08  2:10 ` Simon Marchi
2018-08-09 14:32   ` Joel Brobecker
2018-08-09 14:46     ` Pedro Alves [this message]
2018-08-09 16:07       ` Simon Marchi
2018-08-09 17:19         ` Simon Marchi

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=a0a2c933-b695-0499-2990-7f70bb749ff2@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdbadmin@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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