public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/21494] segfault in find_partial_die_in_comp_unit
       [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
  1 sibling, 0 replies; 2+ messages in thread
From: tromey at sourceware dot org @ 2022-10-21 16:59 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=21494

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug gdb/21494] segfault in find_partial_die_in_comp_unit
       [not found] <bug-21494-4717@http.sourceware.org/bugzilla/>
  2022-10-21 16:59 ` [Bug gdb/21494] segfault in find_partial_die_in_comp_unit tromey at sourceware dot org
@ 2022-10-24  6:27 ` rguenth at gcc dot gnu.org
  1 sibling, 0 replies; 2+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-10-24  6:27 UTC (permalink / raw)
  To: gdb-prs

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-10-24  6:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-21494-4717@http.sourceware.org/bugzilla/>
2022-10-21 16:59 ` [Bug gdb/21494] segfault in find_partial_die_in_comp_unit tromey at sourceware dot org
2022-10-24  6:27 ` rguenth at gcc dot gnu.org

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).