From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: thin_dump segfaults on aarch64-musl
Date: Mon, 12 Oct 2020 03:01:31 +0200 [thread overview]
Message-ID: <20201012010131.azfcjz3vuRvb0pUrHSmawy2V11bET29jvmHMT-o5cTc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25125@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
New comment by duncancmt on void-packages repository
https://github.com/void-linux/void-packages/issues/25125#issuecomment-706801518
Comment:
Excellent!
> Please don't report more issues with this kind of problem until we fixed it.
> Instead, you can make a big issue about aarch64-musl and merge everything there.
Yep! I'll open a new issue with the subject "Exception handling and unwinds segfault on aarch64-musl" and close all these issues as duplicates.
next prev parent reply other threads:[~2020-10-12 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 23:00 [ISSUE] " duncancmt-alt
2020-10-11 4:14 ` ericonr
2020-10-11 4:14 ` ericonr
2020-10-11 19:31 ` duncancmt
2020-10-11 19:46 ` ericonr
2020-10-11 19:46 ` ericonr
2020-10-12 0:49 ` sgn
2020-10-12 1:01 ` duncancmt [this message]
2020-10-12 1:05 ` duncancmt-alt
2020-10-12 1:05 ` [ISSUE] [CLOSED] " duncancmt-alt
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=20201012010131.azfcjz3vuRvb0pUrHSmawy2V11bET29jvmHMT-o5cTc@z \
--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).