From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E445F385E019; Tue, 19 Sep 2023 08:18:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E445F385E019 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1695111535; bh=IQtVAgzqAHSsq+IEczYPb2VZAR/7XpViS8Cq00JfELU=; h=From:To:Subject:Date:From; b=k5spLWQyzPkwexDghXzURD/KwmDj878FGDMW7tMeHuzcZ/BkPAHgcP8dMPjqFeKuN k8avpx5oKe/Wj9ihNAkVVVJRCT1kPaKwisuFoEgz3XpgLnC8IWZIAqeo4zKeUXbPTc Mp+SuFSLoiZIGUva1aFqso0jlC085sFg1bPgVHOU= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/30871] New: [gdb/symtab] Means to control finding debuginfo (without/with sysroot prefix) Date: Tue, 19 Sep 2023 08:18:55 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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=3D30871 Bug ID: 30871 Summary: [gdb/symtab] Means to control finding debuginfo (without/with sysroot prefix) Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- As documented here ( https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html ), there are two ways to find debuginfo: - build-id, and - debug link. The build-id is tried first, then the debug link. Then each case also tries first without, then with sysroot prefix. Together this results in 4 different ways to get to the debuginfo. AFAIK, in the test-suite we have test-cases that exercise the build-id and debug link scenarios individually. But that's not the case for the without/with sysroot prefix cases. It would be good to have a way (say a maintenance command) that determines = the ways in which debug info can be found. That way we could enforce using the with sysroot case. [ This is relevant in the context of containers. Say we have a container, = with an exec and corresponding debug info installed. When we use gdb inside the container to debug the exec, we find the debuginfo using the without sysroot method. When we try the same from outside the container, the without sysro= ot method fails (because the debug info is installed in the container, not outside) and falls back to the with sysroot method, which will look for the debug info inside the container. ] --=20 You are receiving this mail because: You are on the CC list for the bug.=