public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Let ARI allow gdb %p printf extensions
Date: Mon, 14 Oct 2019 22:32:00 -0000	[thread overview]
Message-ID: <cd6fdaa1edac2a543aa23d77f0001f25f45c026b@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT cd6fdaa1edac2a543aa23d77f0001f25f45c026b ***

commit cd6fdaa1edac2a543aa23d77f0001f25f45c026b
Author:     Tom Tromey <tromey@adacore.com>
AuthorDate: Wed Oct 2 10:13:33 2019 -0600
Commit:     Tom Tromey <tromey@adacore.com>
CommitDate: Tue Oct 8 11:16:21 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-08  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 49b468d695..c4c7d5f0f0 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2019-10-08  Tom Tromey  <tromey@adacore.com>
+
+	* contrib/ari/gdb_ari.sh (%p): Allow gdb-specific %p extensions.
+
 2019-10-08  Christian Biesinger  <cbiesinger@google.com>
 
 	* gdbtypes.c (overload_debug): Move comment to header.
diff --git a/gdb/contrib/ari/gdb_ari.sh b/gdb/contrib/ari/gdb_ari.sh
index 4bd434c8fe..7202563f7a 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")
 }
 


             reply	other threads:[~2019-10-14 22:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 22:32 gdb-buildbot [this message]
2019-10-14 22:32 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot
2019-10-15  0:01 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-10-15  0:51 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-10-20 20:16 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2019-10-20 20:42 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2019-10-20 21:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-10-20 21:55 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-10-20 22:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot

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=cd6fdaa1edac2a543aa23d77f0001f25f45c026b@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).