* Re: C++ exceptions seem badly broken with aarch64-musl
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
@ 2019-06-28 8:12 ` voidlinux-github
2019-06-29 23:43 ` voidlinux-github
` (4 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-06-28 8:12 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/7498#issuecomment-506645819
Comment:
`common/cross-profiles/aarch64.sh` has a comment for `XBPS_CFLAGS` which tells `# XXX not yet supported: -fstack-protector-strong` but our `gcc` template enables `--enable-default-ssp` and perhaps `gcc` decides to use the strong stack protection.
I don't know if the comment above still holds true, though.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: C++ exceptions seem badly broken with aarch64-musl
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
2019-06-28 8:12 ` C++ exceptions seem badly broken with aarch64-musl voidlinux-github
@ 2019-06-29 23:43 ` voidlinux-github
2020-04-21 20:42 ` jnbr
` (3 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-06-29 23:43 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
New comment by CMB on void-packages repository
https://github.com/void-linux/void-packages/issues/7498#issuecomment-506994978
Comment:
I tried a rebuild with --enable-default-ssp removed, but no luck,
unfortunately.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: C++ exceptions seem badly broken with aarch64-musl
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
2019-06-28 8:12 ` C++ exceptions seem badly broken with aarch64-musl voidlinux-github
2019-06-29 23:43 ` voidlinux-github
@ 2020-04-21 20:42 ` jnbr
2020-04-21 20:42 ` [ISSUE] [CLOSED] " jnbr
` (2 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: jnbr @ 2020-04-21 20:42 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
New comment by jnbr on void-packages repository
https://github.com/void-linux/void-packages/issues/7498#issuecomment-617403641
Comment:
Doesn't seem to be an issue anymore.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ISSUE] [CLOSED] C++ exceptions seem badly broken with aarch64-musl
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
` (2 preceding siblings ...)
2020-04-21 20:42 ` jnbr
@ 2020-04-21 20:42 ` jnbr
2020-10-12 21:52 ` jnbr
2020-10-12 21:52 ` jnbr
5 siblings, 0 replies; 6+ messages in thread
From: jnbr @ 2020-04-21 20:42 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
Closed issue by CMB on void-packages repository
https://github.com/void-linux/void-packages/issues/7498
Description:
I found this while trying to figure out why mpd segfaults on my Raspberry
Pi 3 running the musl image. ARMv7 with musl does not have the same bug,
neither does aarch64+glibc.
Essentially, a program segfaults whenever an exception is thrown.
The following trivial program will reproduce the issue:
http://sprunge.us/VXR7h6
Expected behavior: the program should print the following on stderr and
abort.
terminate called after throwing an instance of 'Whatever'
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: C++ exceptions seem badly broken with aarch64-musl
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
` (3 preceding siblings ...)
2020-04-21 20:42 ` [ISSUE] [CLOSED] " jnbr
@ 2020-10-12 21:52 ` jnbr
2020-10-12 21:52 ` jnbr
5 siblings, 0 replies; 6+ messages in thread
From: jnbr @ 2020-10-12 21:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
New comment by jnbr on void-packages repository
https://github.com/void-linux/void-packages/issues/7498#issuecomment-707364259
Comment:
This issue is actually not solved. Testing with `QEMU_LD_PREFIX=/usr/aarch64-linux-musl` was wrong, as libstdc++ from `cross-aarch64-linux-musl` is not affected, only the one from package `libstdc++` has the problem.
Further tracking in https://github.com/void-linux/void-packages/issues/7498
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: C++ exceptions seem badly broken with aarch64-musl
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
` (4 preceding siblings ...)
2020-10-12 21:52 ` jnbr
@ 2020-10-12 21:52 ` jnbr
5 siblings, 0 replies; 6+ messages in thread
From: jnbr @ 2020-10-12 21:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
New comment by jnbr on void-packages repository
https://github.com/void-linux/void-packages/issues/7498#issuecomment-707364259
Comment:
This issue is actually not solved. Testing with `QEMU_LD_PREFIX=/usr/aarch64-linux-musl` was wrong, as libstdc++ from `cross-aarch64-linux-musl` is not affected, only the one from package `libstdc++` has the problem.
Further tracking in https://github.com/void-linux/void-packages/issues/25535
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-10-12 21:52 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
2019-06-28 8:12 ` C++ exceptions seem badly broken with aarch64-musl voidlinux-github
2019-06-29 23:43 ` voidlinux-github
2020-04-21 20:42 ` jnbr
2020-04-21 20:42 ` [ISSUE] [CLOSED] " jnbr
2020-10-12 21:52 ` jnbr
2020-10-12 21:52 ` jnbr
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).