From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Oct 2 01:56:22 UTC 2019
Date: Wed, 02 Oct 2019 17:45:00 -0000 [thread overview]
Message-ID: <87k19nt51q.fsf@tromey.com> (raw)
In-Reply-To: <9eebf8fb-43f3-1c13-e557-a71c706b2b73@simark.ca> (Simon Marchi's message of "Wed, 2 Oct 2019 13:39:08 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
Simon> On 2019-10-02 1:35 p.m., Tom Tromey wrote:
>> I believe that in most regexp syntax, a "]" doesn't need to be quoted in
>> a character class, provided it is either the first character (like
>> "[]...]") or comes immediately after the "^" (like "[^]...]").
>>
>> The gawk manual mentions this, though it does also recommend using
>> backslash, so maybe I should just do that.
>>
>> (info "(gawk) Bracket Expressions")
>>
>> To include one of the characters '\', ']', '-', or '^' in a bracket
>> expression, put a '\' in front of it. For example:
>>
>> [d\]]
>>
>> matches either 'd' or ']'. Additionally, if you place ']' right after
>> the opening '[', the closing bracket is treated as one of the characters
>> to be matched.
Simon> Well, as long as the regex does what it is meant to do, I am fine with it.
Simon> I just thought that it would be nice to have a small comment that explains
Simon> what it does, prevent using %p to print raw pointers, but allow the gdb
Simon> extensions.
I went ahead and made both changes.
Tom
commit ab3347cd98e02bb676e85279bc64684b48f4c609
Author: Tom Tromey <tromey@adacore.com>
Date: Wed Oct 2 10:13:33 2019 -0600
Let ARI allow gdb %p printf extensions
As pointed out by Simon, this changes ARI to allow the gdb-specific %p
printf extensions.
gdb/ChangeLog
2019-10-02 Tom Tromey <tromey@adacore.com>
* contrib/ari/gdb_ari.sh (%p): Allow gdb-specific %p extensions.
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index cb450e28730..e79612696e6 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2019-10-02 Tom Tromey <tromey@adacore.com>
+
+ * contrib/ari/gdb_ari.sh (%p): Allow gdb-specific %p extensions.
+
2019-10-02 Tom Tromey <tromey@adacore.com>
* NEWS: Add $_ada_exception entry.
diff --git a/gdb/contrib/ari/gdb_ari.sh b/gdb/contrib/ari/gdb_ari.sh
index 4bd434c8fec..7202563f7a3 100755
--- a/gdb/contrib/ari/gdb_ari.sh
+++ b/gdb/contrib/ari/gdb_ari.sh
@@ -353,7 +353,8 @@ Do not use printf(\"%p\"), instead use printf(\"%s\",paddr()) to dump a \
target address, or host_address_to_string() for a host address"
category["%p"] = ari_code
}
-/%p/ && !/%prec/ {
+# Allow gdb %p extensions, but not other uses of %p.
+/%p[^[\]sF]/ && !/%prec/ {
fail("%p")
}
next prev parent reply other threads:[~2019-10-02 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 1:56 GDB Administrator
2019-10-02 2:50 ` Simon Marchi
2019-10-02 16:15 ` Tom Tromey
2019-10-02 17:02 ` Eli Zaretskii
2019-10-02 17:20 ` Tom Tromey
2019-10-02 17:30 ` Simon Marchi
2019-10-02 17:35 ` Tom Tromey
2019-10-02 17:39 ` Simon Marchi
2019-10-02 17:45 ` Tom Tromey [this message]
2019-10-08 17:16 ` 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=87k19nt51q.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.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