From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2ACAB3858422; Fri, 24 Mar 2023 08:18:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2ACAB3858422 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1679645902; bh=EBDZoIxe/et+qoikfi5QcmFXr+p9LbRQVU4a6sXkniw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=VlPep8TrJvlL4wk4tpldXw1QZi4/eC0kDiKRi02UCoWvkbPyHj2VS5R9P2emOJJor l8+TtgOFxDIiVRn6VOJLCjU1uUCKCtpNI+aqsYI4+b2kyezT5vG2O9wNJ+xssmMtID 1bxfWH52/hwwAMDIIKNIHaO+32xymhQyX9SrrM0U= From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/30265] [gdb/symtab] info var shows incorrect file/line combination for static const class member Date: Fri, 24 Mar 2023 08:18:16 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30265 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom de Vries : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D1985d8cb7048= bcfce60b59cfe219d3b09bda6373 commit 1985d8cb7048bcfce60b59cfe219d3b09bda6373 Author: Tom de Vries Date: Fri Mar 24 09:18:07 2023 +0100 [gdb/testsuite] Fix gdb.cp/m-static.exp regression on Ubuntu 20.04 In commit 722c4596034 ("[gdb/testsuite] Fix gdb.cp/*.exp for remote hos= t"), I needed to change ".*/" into "(.*/)?" in: ... gdb_test "info variable everywhere" \ "File .*/m-static\[.\]h.*const int gnu_obj_4::everywhere;" ... However, due to the fact that I got this output: ... (gdb) info variable everywhere^M All variables matching regular expression "everywhere":^M ^M File /data/vries/gdb/src/gdb/testsuite/gdb.cp/m-static.h:^M 8: const int gnu_obj_4::everywhere;^M ^M File /data/vries/gdb/src/gdb/testsuite/gdb.cp/m-static1.cc:^M 8: const int gnu_obj_4::everywhere;^M ... I decided to make the matching somewhat stricter, to make sure that the= two matched lines were subsequent. The commit turned out to be more strict than intended, and caused a regression on Ubuntu 20.04, where the output was instead: ... (gdb) info variable everywhere^M All variables matching regular expression "everywhere":^M ^M File /data/vries/gdb/src/gdb/testsuite/gdb.cp/m-static.h:^M 8: const int gnu_obj_4::everywhere;^M ... At that point I realized I'm looking at a bug (filed as PR symtab/30265= ), which manifests on openSUSE Leap 15.4 for native and readnow, and on Ub= untu 20.04 for readnow, but not for native. Before my commit, the test-case passed whether the bug manifested or no= t. After my commit, the test-case only passed when the bug manifested. Fix the test-case regression by reverting to the situation before the commit: pass whether the bug manifests or not. We could add an xfail for the P= R, but I'm expecting a fix soon, so that doesn't look worth the effort. Tested on x86_64-linux, both on openSUSE Leap 15.4 and Ubuntu 20.04, bo= th with native and readnow. Reported-By: Simon Marchi --=20 You are receiving this mail because: You are on the CC list for the bug.=