From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D16123858CDA; Thu, 6 Mar 2025 18:37:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D16123858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1741286225; bh=RnUd38YSBX0SMITtSCSbVOXzJ+ooJN0tVGJNs1KM+5M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OdffC+At9Fi0WHqTtZw5IYihnx+6i2t1PQR/i7nNQGl434r/hJfrlM8cNjUtiwi0o ShLmeWbYMpI0ooykcs/HGEGMahcKLmgr0LOFAFB1luWNNOs7som8gCbq49AYpvJfL/ vFlxLjUf6BzqtqCQcrCkQ6Mc8bA8T/LHSF3LmjVQ= From: "pixel@nobis-crew.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/32658] GDB sometimes fails parsing debug information Date: Thu, 06 Mar 2025 18:37:05 +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: pixel@nobis-crew.org X-Bugzilla-Status: UNCONFIRMED 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=3D32658 --- Comment #4 from Nicolas Noble --- I can confirm this patch makes gdb work again properly in my case. I didn't make the connection with signed pointers, but, yes, it makes sense. I have = been bitten previously by this exact quirk. --=20 You are receiving this mail because: You are on the CC list for the bug.=