public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.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 [thread overview]
Message-ID: <bug-21494-4717-2itJwSxKNt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21494-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21494
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(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?
>
> 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 possible
to dig out an old BFD ld and create an affected executable that way (plus old
gdb
to check if the segfault was reproducible).
Not sure if worth - feel free to close the bug instead.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-24 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21494-4717@http.sourceware.org/bugzilla/>
2022-10-21 16:59 ` tromey at sourceware dot org
2022-10-24 6:27 ` rguenth at gcc dot gnu.org [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-21494-4717-2itJwSxKNt@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).