From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
"Cordian A. Daniluk" <th3c0r1uk@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix PR breakpoints/20739: Badly formatted adress string in error message
Date: Tue, 08 Nov 2016 12:48:00 -0000 [thread overview]
Message-ID: <be5815f2-1f63-b2f6-5f5f-4a852baa2c71@redhat.com> (raw)
In-Reply-To: <cb58252ab59139728a09384695133160@polymtl.ca>
On 10/29/2016 08:57 PM, Simon Marchi wrote:
>> old_chain = make_cleanup (xfree, msg);
>>
>> if (!rslt)
>> - error (_("May not have a fast tracepoint at 0x%s%s"),
>> + error (_("May not have a fast tracepoint at %s%s"),
>> paddress (sarch, sal->pc), (msg ? msg : ""));
>>
>> do_cleanups (old_chain);
>
> That seems like an obvious fix to me, thanks for addressing it.
Agreed.
> That means to put the PR mention above the list of files. The
> description should tell more or less precisely _what_ has changed (and
> not _why_ it was changed, that belongs to the commit message, which is
> already clear in your case).
>
> For example:
>
> PR breakpoints/20739
> * breakpoint.c (check_fast_tracepoint_sals): Don't print duplicate 0x
> prefix.
Thanks, I copied that into the patch.
> I don't see your name in MAINTAINERS, do you have write access to the
> repo? If you plan to contribute patches regularly, it would be a good
> idea for you to go through the process to get it (you'll need assistance
> from one of the global maintainers). Otherwise, somebody else with
> write access can push it for you.
I've pushed it in now, as below.
From 53c3572a9f5b03a92292cb6d24bf69b52c95500e Mon Sep 17 00:00:00 2001
From: "Cordian A. Daniluk" <th3c0r1uk@gmail.com>
Date: Sat, 29 Oct 2016 20:39:57 +0200
Subject: [PATCH] Fix PR breakpoints/20739: Badly formatted adress string in
error message
Remove duplicate `0x'-prefix for the hex address printed. `paddress'
already prepends this, so no need to do it manually.
gdb/ChangeLog:
2016-11-08 Cordian A. Daniluk <th3c0r1uk@gmail.com>
PR breakpoints/20739
* breakpoint.c (check_fast_tracepoint_sals): Don't print duplicate
0x prefix.
---
gdb/ChangeLog | 6 ++++++
gdb/breakpoint.c | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index db5ec9b..099c63e 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,9 @@
+2016-11-08 Cordian A. Daniluk <th3c0r1uk@gmail.com>
+
+ PR breakpoints/20739
+ * breakpoint.c (check_fast_tracepoint_sals): Don't print duplicate
+ 0x prefix.
+
2016-11-08 Yao Qi <yao.qi@linaro.org>
* rust-lang.c (val_print_struct): Fix indentation.
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 3908dab..9f9cb8a 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -9653,7 +9653,7 @@ check_fast_tracepoint_sals (struct gdbarch *gdbarch,
old_chain = make_cleanup (xfree, msg);
if (!rslt)
- error (_("May not have a fast tracepoint at 0x%s%s"),
+ error (_("May not have a fast tracepoint at %s%s"),
paddress (sarch, sal->pc), (msg ? msg : ""));
do_cleanups (old_chain);
--
2.5.5
prev parent reply other threads:[~2016-11-08 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 16:40 Cordian A. Daniluk
2016-10-29 19:57 ` Simon Marchi
2016-11-08 12:48 ` Pedro Alves [this message]
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=be5815f2-1f63-b2f6-5f5f-4a852baa2c71@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=th3c0r1uk@gmail.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