From: Julia DeMille <me@jdemille.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libsupc++: Fix UB terminating on foreign exception
Date: Mon, 15 Jan 2024 11:31:05 -0600 [thread overview]
Message-ID: <a93167e5-b2c5-43d1-a3d3-b44107c38847@jdemille.com> (raw)
In-Reply-To: <fcfddbf6-5cd9-4956-97a7-40a35f9d8656@jdemille.com>
Some more info:
On 2024-01-14 21:39, Julia DeMille wrote:
> I've gotten this to work, and run into an unexpected situation.
> Something about the personality routine is causing a SIGABRT.
> Investigating further.
This occurs due to an assertion in _Unwind_SetGR. Seemingly, the
compiler intrinsic `__builtin_eh_return_data_regno` is doing something
it *really* should not. I'm not a compiler developer, and have no clue
how to investigate this.
This issue does not occur with Rust.
Additionally, LLVM's libc++abi manages not only to cleanly handle a Rust
panic, but also, through some voodoo magic that took me by surprise,
recognize Objective-C exceptions (and provide info on them) in its
terminate handler. Perhaps due to Objective-C++? Hell if I know.
Thought it was worth mentioning that other implementations *have* gotten
this working, though.
--
Thanks,
Julia DeMille
she/her
next prev parent reply other threads:[~2024-01-15 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 0:05 Julia DeMille
2024-01-14 1:17 ` Andrew Pinski
2024-01-14 1:34 ` Julia DeMille
2024-01-14 7:52 ` Jonathan Wakely
2024-01-15 0:51 ` Julia DeMille
2024-01-15 3:39 ` Julia DeMille
2024-01-15 17:31 ` Julia DeMille [this message]
2024-04-09 17:24 ` Julia DeMille
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=a93167e5-b2c5-43d1-a3d3-b44107c38847@jdemille.com \
--to=me@jdemille.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=pinskia@gmail.com \
/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).