public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dimitar.yordanov at sap dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/111731] [13/14 regression] gcc_assert is hit at libgcc/unwind-dw2-fde.c#L291
Date: Mon, 11 Mar 2024 12:41:58 +0000 [thread overview]
Message-ID: <bug-111731-4-EFX4yOi82Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111731-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111731
--- Comment #5 from Dimitar Yordanov <dimitar.yordanov at sap dot com> ---
> It looks like the code does not find an unwind frame when de-registering an exception handler
From what I understand so far the issue is already there when doing the
registration. There is twice a call to btree_insert:
btree_insert (®istered_frames, (uintptr_type) begin, 1, ob);
btree_insert (®istered_frames, range[0], range[1] - range[0], ob);
for those, calls when "range[0]" is before "begin" with the same "ob" the next
search for removing will return the slot where range[0] is not the one of
begin. Because of the way "btree_node_find_leaf_slot" works, doing a
if (n->content.entries[index].base + n->content.entries[index].size > value)
which is true for the second insert call even if we want to find the slot for
the first insert.
next prev parent reply other threads:[~2024-03-11 12:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 2:17 [Bug libgcc/111731] New: " crazylht at gmail dot com
2023-10-09 2:18 ` [Bug libgcc/111731] " crazylht at gmail dot com
2023-10-09 2:20 ` crazylht at gmail dot com
2023-10-09 9:57 ` rguenth at gcc dot gnu.org
2024-03-11 11:51 ` dimitar.yordanov at sap dot com
2024-03-11 12:03 ` tneumann at users dot sourceforge.net
2024-03-11 12:41 ` dimitar.yordanov at sap dot com [this message]
2024-03-11 12:55 ` dimitar.yordanov at sap dot com
2024-03-11 12:58 ` tneumann at users dot sourceforge.net
2024-03-11 12:59 ` dimitar.yordanov at sap dot com
2024-03-11 13:02 ` tneumann at users dot sourceforge.net
2024-03-11 13:39 ` dimitar.yordanov at sap dot com
2024-03-11 13:45 ` tneumann at users dot sourceforge.net
2024-03-11 14:10 ` dimitar.yordanov at sap dot com
2024-03-11 18:00 ` jakub at gcc dot gnu.org
2024-03-11 19:52 ` tneumann at users dot sourceforge.net
2024-03-12 6:27 ` tneumann at users dot sourceforge.net
2024-03-12 6:29 ` liuhongt at gcc dot gnu.org
2024-03-13 17:57 ` dimitar.yordanov at sap dot com
2024-03-14 6:48 ` tneumann at users dot sourceforge.net
2024-03-15 9:14 ` dimitar.yordanov at sap dot com
2024-03-22 14:08 ` cvs-commit at gcc dot gnu.org
2024-04-02 8:37 ` cvs-commit at gcc dot gnu.org
2024-04-02 11:24 ` rguenth 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-111731-4-EFX4yOi82Z@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).