From: Yao Qi <yao@codesourcery.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Feb 16 01:53:55 UTC 2011
Date: Wed, 16 Feb 2011 10:09:00 -0000 [thread overview]
Message-ID: <4D5B9DA7.8050204@codesourcery.com> (raw)
In-Reply-To: <006601cbcdb4$e8381cf0$b8a856d0$@muller@ics-cnrs.unistra.fr>
[-- Attachment #1: Type: text/plain, Size: 183 bytes --]
On 02/16/2011 04:38 PM, Pierre Muller wrote:
> Hi Yao,
>
> could you please modify this patch
> so as to also remove the trailing newline?
Sure. Applied.
--
Yao (é½å°§)
[-- Attachment #2: ari_thread.patch --]
[-- Type: text/x-patch, Size: 1050 bytes --]
Index: gdb/ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.12591
diff -u -r1.12591 ChangeLog
--- gdb/ChangeLog 15 Feb 2011 21:43:24 -0000 1.12591
+++ gdb/ChangeLog 16 Feb 2011 09:45:02 -0000
@@ -1,3 +1,8 @@
+2011-02-16 Yao Qi <yao@codesourcery.com>
+
+ * thread.c (info_threads_command): Add missing i18n markup and remove
+ trailing newline.
+
2011-02-15 Paul Pluzhnikov <ppluzhnikov@google.com>
* breakpoint.c (longjmp_names): New variable.
Index: gdb/thread.c
===================================================================
RCS file: /cvs/src/src/gdb/thread.c,v
retrieving revision 1.132
diff -u -r1.132 thread.c
--- gdb/thread.c 15 Feb 2011 21:17:52 -0000 1.132
+++ gdb/thread.c 16 Feb 2011 09:45:02 -0000
@@ -980,7 +980,7 @@
unsigned int highrange;
if (tmp_tid <= 0)
- error ("invalid thread id %d\n", tmp_tid);
+ error (_("invalid thread id %d"), tmp_tid);
tid = tmp_tid;
print_thread_info (uiout, tid, -1);
next prev parent reply other threads:[~2011-02-16 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 3:28 GDB Administrator
2011-02-16 6:44 ` Yao Qi
2011-02-16 9:29 ` Pierre Muller
2011-02-16 10:09 ` Yao Qi [this message]
2011-02-16 18:10 ` Michael Snyder
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=4D5B9DA7.8050204@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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