public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31514] [gdb/testsuite] FAIL: gdb.ada/tagged-lookup.exp: only one CU expanded
Date: Mon, 25 Mar 2024 14:28:46 +0000	[thread overview]
Message-ID: <bug-31514-4717-JXXjBitLvx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31514-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31514

--- Comment #9 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=874f4887f0361e953f7098459ae60a5f894d362a

commit 874f4887f0361e953f7098459ae60a5f894d362a
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Mar 25 15:28:35 2024 +0100

    [gdb/testsuite] Fix gdb.ada/tagged-lookup.exp with gcc <= 12

    With gcc 13, test-case gdb.ada/tagged-lookup.exp passes for me, but with
gcc
    12, I get:
    ...
    (gdb) set debug symtab-create 1^M
    (gdb) print *the_local_var^M
      ...
    $1 = (n => 2)^M
    (gdb) FAIL: gdb.ada/tagged-lookup.exp: only one CU expanded
    ...

    The problem is that this fails:
    ...
        -re -wrap ".* = \\\(n => $decimal\\\)" {
            if {$found_pck + $found_pck2 == 1} {
                pass $gdb_test_name
            } else {
                fail $gdb_test_name
            }
    ...
    because $found_pck == 0 and $found_pck2 == 0.

    Indeed, with gcc 13 we have:
    ...
    $ grep "start_subfile: name = .*/tagged-lookup/" gdb.log | sed 's%.*/%%'
    b~foo.adb
    b~foo.adb
    b~foo.adb
    b~foo.ads
    pck2.adb
    pck2.adb
    pck2.ads
    pck2.adb
    pck2.ads
    ...
    and with gcc 12:
    ...
    $ grep "start_subfile: name = .*/tagged-lookup/" gdb.log | sed 's%.*/%%'
    b~foo.adb
    b~foo.adb
    b~foo.adb
    b~foo.ads
    ...

    Fix this by checking for "$found_pck + $found_pck2 <= 1" instead.

    Tested on x86_64-linux.

    Approved-By: Tom Tromey <tom@tromey.com>

    PR testsuite/31514
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31514

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-03-25 14:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 10:24 [Bug testsuite/31514] New: " vries at gcc dot gnu.org
2024-03-20 15:31 ` [Bug testsuite/31514] " vries at gcc dot gnu.org
2024-03-20 15:57 ` vries at gcc dot gnu.org
2024-03-20 16:37 ` vries at gcc dot gnu.org
2024-03-20 16:38 ` vries at gcc dot gnu.org
2024-03-21  7:34 ` vries at gcc dot gnu.org
2024-03-21  7:50 ` vries at gcc dot gnu.org
2024-03-21  8:00 ` vries at gcc dot gnu.org
2024-03-25 14:06 ` vries at gcc dot gnu.org
2024-03-25 14:28 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-25 14:29 ` 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-31514-4717-JXXjBitLvx@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).