From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 480103856DC2; Thu, 11 May 2023 21:48:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 480103856DC2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1683841700; bh=vX4GYIVz7TCF1sGoDZxJ73I74HF598eSyEki6nevyVs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FzLJUKfoa2K0h64kxhHKAda2+3BSn/xHIIVoiMIZAKwHwhnITK+kTR6GhlLc1Gdd1 bC+NSXfE1lmbOpkLobisExVLiH6mYde0HeSFpNDpp6mEuRGUt+0RYwByO0LMsC/9SI JQUYiRdDLUL7UdMYEIkIwOEgWvJ85gi/JIzkPGOs= From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/30296] GDB showing for struct members that are clearly not. Date: Thu, 11 May 2023 21:48:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb 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: tromey 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=3D30296 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D245f9db1fa8a= 355e9b18d0966fe20d6341e36813 commit 245f9db1fa8a355e9b18d0966fe20d6341e36813 Author: Tom Tromey Date: Thu Apr 20 15:47:41 2023 -0600 Do not print when piece is optimized out A user reported a bug where printing a certain array of integer types would result in the nonsensical: (gdb) p l_126 $1 =3D {6639779683436459270, , , } I tracked this down to some issues in the DWARF expression code. First, check_pieced_synthetic_pointer did not account for the situation where a location expression does not describe all the bits of a value -- in this case it returned true, meaning there is a synthetic pointer, but in fact these bits are optimized out. (It turns out this incorrect output had already been erroneously tested for as well.) Next, rw_pieced_value did not mark these bits as optimized-out, either. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30296 --=20 You are receiving this mail because: You are on the CC list for the bug.=