* Re: thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl duncancmt-alt
@ 2020-10-11 4:14 ` ericonr
2020-10-11 4:14 ` ericonr
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: ericonr @ 2020-10-11 4:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/25125#issuecomment-706647212
Comment:
> If anyone could provide some insight into what's broken, I would be greatly appreciative.
I believe the current theory is that there are issues with any unwinding actions. That's as far as I understand the issue, sorry.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl duncancmt-alt
2020-10-11 4:14 ` ericonr
@ 2020-10-11 4:14 ` ericonr
2020-10-11 19:31 ` duncancmt
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: ericonr @ 2020-10-11 4:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/25125#issuecomment-706647212
Comment:
> If anyone could provide some insight into what's broken, I would be greatly appreciative.
I believe the current theory is that there are issues with any unwinding actions. That's as far as I understand the issue, sorry.
Thanks for reporting all bugs!
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl 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
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: duncancmt @ 2020-10-11 19:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
New comment by duncancmt on void-packages repository
https://github.com/void-linux/void-packages/issues/25125#issuecomment-706756380
Comment:
> I believe the current theory is that there are issues with any unwinding actions.
That's very interesting. Is there anything more that I can do to help debug this problem? What do you mean by "unwinding actions"? Exception handlers in C++? If I could run `gdb`, I would debug it further myself. If there's further discussion about this bug in another thread/forum, I would be happy to assist.
It may also be of interest, I have posted another report in a similar vein, but one that has a very simple command-line difference between the working and the non-working case #25531
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl duncancmt-alt
` (2 preceding siblings ...)
2020-10-11 19:31 ` duncancmt
@ 2020-10-11 19:46 ` ericonr
2020-10-11 19:46 ` ericonr
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: ericonr @ 2020-10-11 19:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/25125#issuecomment-706758251
Comment:
> Exception handlers in C++?
That and probably `libunwind` as well. We talked about it on IRC a bit (`#xbps` on freenode).
Regarding this specific bug, is it straceable?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl duncancmt-alt
` (3 preceding siblings ...)
2020-10-11 19:46 ` ericonr
@ 2020-10-11 19:46 ` ericonr
2020-10-12 0:49 ` sgn
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: ericonr @ 2020-10-11 19:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/25125#issuecomment-706758251
Comment:
> Exception handlers in C++?
That and probably `libunwind` as well. We talked about it on IRC a bit (`#xbps` on freenode).
Glad you got your account back!
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl duncancmt-alt
` (4 preceding siblings ...)
2020-10-11 19:46 ` ericonr
@ 2020-10-12 0:49 ` sgn
2020-10-12 1:01 ` duncancmt
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: sgn @ 2020-10-12 0:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/25125#issuecomment-706798828
Comment:
@duncancmt ~This simple C++ program crashed on `aarch64-musl`, MCVE identified. `gdb` itself uses exception, so gdb couldn't help. 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. Thanks
```cpp
#include <string>
#include <stdexcept>
int main(int argc, char **argv) {
try {
throw std::runtime_error("hello");
} catch (const std::exception& e) {
}
return 0;
}
```
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl duncancmt-alt
` (5 preceding siblings ...)
2020-10-12 0:49 ` sgn
@ 2020-10-12 1:01 ` duncancmt
2020-10-12 1:05 ` duncancmt-alt
2020-10-12 1:05 ` [ISSUE] [CLOSED] " duncancmt-alt
8 siblings, 0 replies; 10+ messages in thread
From: duncancmt @ 2020-10-12 1:01 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl duncancmt-alt
` (6 preceding siblings ...)
2020-10-12 1:01 ` duncancmt
@ 2020-10-12 1:05 ` duncancmt-alt
2020-10-12 1:05 ` [ISSUE] [CLOSED] " duncancmt-alt
8 siblings, 0 replies; 10+ messages in thread
From: duncancmt-alt @ 2020-10-12 1:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
New comment by duncancmt-alt on void-packages repository
https://github.com/void-linux/void-packages/issues/25125#issuecomment-706802657
Comment:
duplicates #25535
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [ISSUE] [CLOSED] thin_dump segfaults on aarch64-musl
2020-09-26 23:00 [ISSUE] thin_dump segfaults on aarch64-musl duncancmt-alt
` (7 preceding siblings ...)
2020-10-12 1:05 ` duncancmt-alt
@ 2020-10-12 1:05 ` duncancmt-alt
8 siblings, 0 replies; 10+ messages in thread
From: duncancmt-alt @ 2020-10-12 1:05 UTC (permalink / raw)
To: ml
[-- 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)
^ permalink raw reply [flat|nested] 10+ messages in thread