From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@gnat.com>, Tom Tromey <tom@tromey.com>
Subject: [committed][gdb/testsuite] Add PR number in KFAIL in gdb.ada/array_ptr_renaming.exp
Date: Tue, 28 Apr 2020 06:27:34 +0200 [thread overview]
Message-ID: <20200428042732.GA10165@delia> (raw)
Hi,
When running test-case gdb.ada/array_ptr_renaming.exp we run into:
...
(gdb) print ntp^M
$3 = (3 => 30, 40)^M
(gdb) KFAIL: gdb.ada/array_ptr_renaming.exp: print ntp (PRMS: gdb/NNNN)
...
I've opened PR25883 for this failure. Reference the PR from the KFAIL, such
that we have:
...
KFAIL: gdb.ada/array_ptr_renaming.exp: print ntp (PRMS: gdb/25883)
...
Committed to trunk.
Thanks,
- Tom
[gdb/testsuite] Add PR number in KFAIL in gdb.ada/array_ptr_renaming.exp
gdb/testsuite/ChangeLog:
2020-04-28 Tom de Vries <tdevries@suse.de>
* gdb.ada/array_ptr_renaming.exp: Add PR number in KFAIL.
---
gdb/testsuite/gdb.ada/array_ptr_renaming.exp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/testsuite/gdb.ada/array_ptr_renaming.exp b/gdb/testsuite/gdb.ada/array_ptr_renaming.exp
index 8dd10426af2..e568b60b1e4 100644
--- a/gdb/testsuite/gdb.ada/array_ptr_renaming.exp
+++ b/gdb/testsuite/gdb.ada/array_ptr_renaming.exp
@@ -33,7 +33,7 @@ gdb_test "print nt(1)" " = 10"
# representation with GNAT (fat pointers). In this case, GDB "forgets" that
# it's dealing with an access and prints directly the array contents. This
# should be fixed some day.
-setup_kfail "gdb/NNNN" *-*-*
+setup_kfail "gdb/25883" *-*-*
gdb_test "print ntp" " = \\(access pack\\.table_type\\) $hex.*"
gdb_test "print ntp.all" " = \\(3 => 30, 40\\)"
gdb_test "print ntp(3)" " = 30"
reply other threads:[~2020-04-28 4:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200428042732.GA10165@delia \
--to=tdevries@suse.de \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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