public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/26997] [-m32] FAIL: gdb.fortran/array-slices.exp: repack=on: test 9: check sizes match
Date: Wed, 02 Dec 2020 15:29:23 +0000 [thread overview]
Message-ID: <bug-26997-4717-KHmIE3BNCJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26997-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26997
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
With some additional logging:
....
diff --git a/gdb/testsuite/gdb.fortran/array-slices.exp
b/gdb/testsuite/gdb.fortran/array-s
lices.exp
index ff00fae886..a9a64aaa3f 100644
--- a/gdb/testsuite/gdb.fortran/array-slices.exp
+++ b/gdb/testsuite/gdb.fortran/array-slices.exp
@@ -226,7 +226,9 @@ proc run_test { repack } {
# sizes when GDB's repacking setting matches the repacking
# behaviour we got from the compiler.
if { ($addr_in_show < $start_addr || $addr_in_show >= $end_addr) \
- == ($repack == "on") } {
+ == ($repack == "on") } {
+ verbose -log "size_in_show: $size_in_show"
+ verbose -log "size_in_parent: $size_in_parent"
gdb_assert {$size_in_show == $size_in_parent} \
"check sizes match"
} elseif { $repack == "off" } {
....
we have:
...
size_in_show: 3136
size_in_parent: 16
FAIL: gdb.fortran/array-slices.exp: repack=on: test 9: check sizes match
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-02 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 15:18 [Bug testsuite/26997] New: " vries at gcc dot gnu.org
2020-12-02 15:29 ` vries at gcc dot gnu.org [this message]
2020-12-02 18:48 ` [Bug testsuite/26997] " vries at gcc dot gnu.org
2021-01-08 14:14 ` vries at gcc dot gnu.org
2021-01-08 14:17 ` vries at gcc dot gnu.org
2021-01-15 10:04 ` vries at gcc dot gnu.org
2021-01-15 11:14 ` cvs-commit at gcc dot gnu.org
2021-01-15 11:15 ` vries at gcc dot gnu.org
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=bug-26997-4717-KHmIE3BNCJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).