From: duncancmt-alt <duncancmt-alt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] thin_dump segfaults on aarch64-musl
Date: Mon, 12 Oct 2020 03:05:48 +0200 [thread overview]
Message-ID: <20201012010548.qXgGgWfCOsTV8MOB-ECxN0HtgFsJ0TS69hPI3wyhb7Y@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: 1709 bytes --]
Closed issue by duncancmt-alt on void-packages repository
https://github.com/void-linux/void-packages/issues/25125
Description:
Yet another report in my "PACKAGE segfaults on aarch64-musl" series. See also #24783 #24785 and #24918 (more to come, I'm sure). I regret that I am posting this from a different account. I am currently locked out of my usual machine due to a bug in LVM2 (which I hope is unrelated to the issue at hand). See [this thread on the lvm-linux mailing list](https://www.redhat.com/archives/linux-lvm/2020-September/msg00088.html) and [this bug open upstream](https://bugzilla.redhat.com/show_bug.cgi?id=1882483).
But hopefully that's all unrelated.
### System
* xuname:
`Void 5.7.0_1 aarch64-musl Unknown uptodate rFF`
* package:
`thin-provisioning-tools-0.8.5_1`
### Expected behavior
```
# thin_dump /dev/null
<no segfault, maybe an error message or something?>
```
### Actual behavior
```
# thin_dump /dev/null
Segmentation fault
```
### Steps to reproduce the behavior
See above
### Other remarks
I've [uploaded a tarball](https://drive.google.com/file/d/1RnUFlSMmFph5JXxenDJ1PhuCLV9xelAc/view?usp=sharing) containing the relevant binary, shared libraries, and core dump. I regret that I cannot provide a backtrace, but `gdb` is broken on aarch64-musl (see #24785 ).
Something appears to be seriously wrong with aarch64-musl. If anyone could provide some insight into what's broken, I would be greatly appreciative. Otherwise, I think a reasonable person may conclude that despite documentation otherwise, aarch64-musl is *not* actually supported on void (or at least, it's barely usable what with how many broken packages there are)
prev parent reply other threads:[~2020-10-12 1:05 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
2020-10-12 1:05 ` duncancmt-alt
2020-10-12 1:05 ` duncancmt-alt [this message]
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=20201012010548.qXgGgWfCOsTV8MOB-ECxN0HtgFsJ0TS69hPI3wyhb7Y@z \
--to=duncancmt-alt@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).