From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E9E443858D3C; Tue, 12 Sep 2023 10:01:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E9E443858D3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1694512879; bh=kFf6JsohaQR/YZT6v7N6D0aZG7/1HCyycce18OjDssI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=iDIWMxKzudI4xv5GMqi1O8XrVK8hF6r2Rq6athtNokD365GP5OMRanYMm0AP/zwDs jVwBffE8MLh86R/WLK0p8lhgjGyZEAjKuCtEZYh9DmmuI752uK2Umam/n8F1pAcUHH 9HW+8CoQ3mcuVsljjiXLd46u83Y22uJaVP43kQbI= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/30829] [gdb/symtab] Review write_gdbindex for dwz Date: Tue, 12 Sep 2023 10:01:19 +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: minor 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: 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=3D30829 --- Comment #7 from Tom de Vries --- (In reply to Tom de Vries from comment #3) > There seems to be some undocumented behaviour going on (at least, I don't > see any explicit mention of the following here: > https://sourceware.org/gdb/onlinedocs/gdb/Index-Section-Format.html#Index- > Section-Format ). >=20 > Indeed each .gdb_index section has a CU/TU table, and the section for the > .gnu_debugaltlink file contains nothing else. >=20 > I think the assumption was that a .gnu_debugaltlink contains only PUs, and > that the toplevel symbol table only contains references to CUs/TUs, which > will be pointing to the toplevel CU/TU table. >=20 > However, in this test-case the .gnu_debugaltlink file contains a CU. >=20 > And the reference in the toplevel symbol table point towards it, in the > sense that the virtual toplevel CU/TU table (otherwise known as all_units) > first contains the toplevel CU/PUs, then toplevel TUs, then > .gnu_debugaltlink CU/PUs I've submitted a doc patch: https://sourceware.org/pipermail/gdb-patches/2023-September/202359.html --=20 You are receiving this mail because: You are on the CC list for the bug.=