From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 47DF538582A8; Mon, 24 Oct 2022 06:27:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 47DF538582A8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1666592842; bh=FsaorHm5LafUssWD+KrjcmvopU5hQIFd5QLeLSJxXyc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bi7azNkkLMayc2HFE2L2x2gm28rmJYCCAoJuVE4d3jpjSc39zCZpyBspGWxEIscnQ SY/0unNtgT6s6FXn8aB+Uoy8UqKYcs/Af3JcIwie9siRG2AxCcCAaDA9t022CsKi5M 4KxgBy4+l1ir9cUbmdQdBe5SW7HBNkenVsHPbW8o= From: "rguenth at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/21494] segfault in find_partial_die_in_comp_unit Date: Mon, 24 Oct 2022 06:27:21 +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: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth 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=3D21494 --- Comment #4 from Richard Biener --- (In reply to Tom Tromey from comment #3) > Is it still possible to create an executable with this flaw? > Or is the linker bug fixed and now it's gone? >=20 > The DWARF scanner is rewritten so I don't know if the original > problem occurs or not. The linker bug was meanwhile fixed. Unfortunately I didn't save any of the broken executables - the referenced bug says libstdc++ tests were broken, but as far as I remember every executable compiled with -g -flto -Wl,--gc-sections was broken due to stripped relocations. It might be poss= ible to dig out an old BFD ld and create an affected executable that way (plus o= ld gdb to check if the segfault was reproducible). Not sure if worth - feel free to close the bug instead. --=20 You are receiving this mail because: You are on the CC list for the bug.=