public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66874] RFE: x86_64_fallback_frame_state more robust
Date: Fri, 23 Feb 2024 17:24:30 +0000 [thread overview]
Message-ID: <bug-66874-4-IlzwPsDPEs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66874-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66874
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Sam James from comment #2)
> I've been going crazy hitting this recently (see e.g.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114068#c2).
>
> pinskia pointed me here and I fear I might be hitting this as a result of
> dwz optimised debug info on gcc (as it's the only recent change I can think
> of).
How could dwz have anything to do with this? The libgcc unwinder works on
.eh_frame sections. dwz only ever modifies .debug_* sections (and
.gnu_debugaltlink and
perhaps throws away .gdb_index), all non-allocatable sections which the libgcc
unwinder never touches.
next prev parent reply other threads:[~2024-02-23 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 23:58 [Bug libgcc/66874] New: " jreiser at bitwagon dot com
2015-07-15 3:04 ` [Bug libgcc/66874] " hjl.tools at gmail dot com
2024-02-23 17:19 ` [Bug target/66874] " sjames at gcc dot gnu.org
2024-02-23 17:24 ` jakub at gcc dot gnu.org [this message]
2024-02-23 17:25 ` sjames at gcc dot gnu.org
2024-02-23 19:39 ` schwab@linux-m68k.org
2024-02-26 15:08 ` sjames at gcc dot gnu.org
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-66874-4-IlzwPsDPEs@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).