From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 65205385780A; Fri, 29 Jul 2022 16:25:07 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 65205385780A
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/29426] FAIL: gdb.mi/mi-var-invalidate.exp: linteger not
 anymore in scope due to binary changes (unexpected output)
Date: Fri, 29 Jul 2022 16:25:07 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: mi
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries 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: <bug-29426-4717-9AULgzYaLJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29426-4717@http.sourceware.org/bugzilla/>
References: <bug-29426-4717@http.sourceware.org/bugzilla/>
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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2022 16:25:07 -0000

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

--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Lancelot SIX from comment #8)
> Created attachment 14242 [details]
> add_varobj_global_flag.patch
>=20
> This regression also shows an interesting problem.
>=20
> Currently, when we unload an objfile and find a varobj which is linked to=
 a
> block from this objfile, we clear the valid_block pointer to avoid having=
 a
> stall pointer.  However by doing this, we loose the ability to distinguis=
h a
> varobj tracking a global (no valid_block associated) to a varobj tracking=
 a
> local (some valid_block associated).  Later, when we reload a new program
> and try to recreate varobj for globals, we have false positive and also t=
ry
> to recreate some locals as well.
>=20
> The attached patch fixes this, but some differences remain whether I
> ubuntu=E2=80=99s stock GCC or custom built HEAD GCC.

Ack, this fixes the gdb.mi/mi-var-invalidate.exp regression for me.

But I still see:
...
$ grep ^FAIL: gdb.sum=20
FAIL: gdb.mi/mi-var-invalidate-shlib.exp: separate_debuginfo=3D0: in new pr=
ocess:
global_var recreated (unexpected output)
FAIL: gdb.mi/mi-var-invalidate-shlib.exp: separate_debuginfo=3D1: in new pr=
ocess:
global_var recreated (unexpected output)
...

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