From: Mark Wielaard <mjw@redhat.com>
To: GDB Administrator <gdbadmin@sourceware.org>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Sat Jan 24 01:55:33 UTC 2015
Date: Sat, 24 Jan 2015 20:14:00 -0000 [thread overview]
Message-ID: <20150124141517.GB19834@blokker.redhat.com> (raw)
In-Reply-To: <20150124141250.GA19834@blokker.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
On Sat, Jan 24, 2015 at 03:12:50PM +0100, Mark Wielaard wrote:
> Hi,
>
> On Sat, Jan 24, 2015 at 01:55:34AM +0000, GDB Administrator wrote:
> > 645a646
> > > gdb/stack.c:2467: gettext: _ markup: All messages should be marked up with _.
> > gdb/stack.c:2467: warning ("Function does not return normally to caller.");
>
> I think that is caused by my patch and the fix seems to simply add the _
> as attached. OK to push?
Sorry, forgot to attach. Now it is.
> How do I run these ARI checks locally? And could the buildbot do them?
>
> Thanks,
>
> Mark
[-- Attachment #2: 0001-Fix-ARI-warning-in-stack.c-return_command.patch --]
[-- Type: text/plain, Size: 1182 bytes --]
From 0ad193d0a8b80fbf32717ee7f88288f7552b12de Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mjw@redhat.com>
Date: Sat, 24 Jan 2015 15:08:32 +0100
Subject: [PATCH] Fix ARI warning in stack.c (return_command).
gdb/ChangeLog
* stack.c (return_command): Markup warning message with _.
---
gdb/ChangeLog | 4 ++++
gdb/stack.c | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 10c3855..6b89515 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2015-01-24 Mark Wielaard <mjw@redhat.com>
+
+ * stack.c (return_command): Markup warning message with _.
+
2015-01-23 Simon Marchi <simon.marchi@ericsson.com>
PR gdb/17416
diff --git a/gdb/stack.c b/gdb/stack.c
index 5f2a3dc..5831999 100644
--- a/gdb/stack.c
+++ b/gdb/stack.c
@@ -2464,7 +2464,7 @@ return_command (char *retval_exp, int from_tty)
else
{
if (TYPE_NO_RETURN (thisfun->type))
- warning ("Function does not return normally to caller.");
+ warning (_("Function does not return normally to caller."));
confirmed = query (_("%sMake %s return now? "), query_prefix,
SYMBOL_PRINT_NAME (thisfun));
}
--
1.8.3.1
next prev parent reply other threads:[~2015-01-24 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 13:31 GDB Administrator
2015-01-24 19:24 ` Mark Wielaard
2015-01-24 20:14 ` Mark Wielaard [this message]
2015-01-26 13:02 ` Yao Qi
2015-01-26 16:19 ` Mark Wielaard
2015-01-26 17:19 ` Yao Qi
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=20150124141517.GB19834@blokker.redhat.com \
--to=mjw@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=gdbadmin@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