From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Exception handling and stack unwinds segfault on aarch64-musl
Date: Mon, 12 Oct 2020 03:02:29 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25535@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
New issue by duncancmt on void-packages repository
https://github.com/void-linux/void-packages/issues/25535
Description:
`gdb` itself uses exception, so gdb couldn't help. Please don't report more issues with this kind of problem until we fixed it.
```cpp
#include <string>
#include <stdexcept>
int main(int argc, char **argv) {
try {
throw std::runtime_error("hello");
} catch (const std::exception& e) {
}
return 0;
}
```
_Originally posted by @sgn in https://github.com/void-linux/void-packages/issues/25125#issuecomment-706798828_
next reply other threads:[~2020-10-12 1:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 1:02 duncancmt [this message]
2020-10-12 19:10 ` jnbr
2020-10-12 23:44 ` sgn
2020-10-12 23:45 ` sgn
2020-10-14 10:17 ` jnbr
2020-10-14 19:34 ` jnbr
2020-10-14 19:34 ` jnbr
2020-10-16 18:29 ` [ISSUE] [CLOSED] " jnbr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25535@inbox.vuxu.org \
--to=duncancmt@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).