From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [RFC] libexecinfo broken on musl
Date: Sun, 18 Dec 2022 06:23:32 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41159@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]
New issue by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/41159
Description:
<!--
if you are creating a bug report or package request, please fill out one of the forms here:
https://github.com/void-linux/void-packages/issues/new/choose
Don't request an update of a package, We have a script for that:
https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt
However, a quality pull request may help.
-->
This was something noticed by sgn and I when debugging the ldc crash on musl when testing the gcc 12 update.
When a segfault occurs, instead of printing the stack trace, libexecinfo either returns 0 or segfaults. (ultimately not really accomplishing anything)
This is something that was noticed in Alpine as well:
https://gitlab.alpinelinux.org/alpine/aports/-/issues/10896
Alpine came to a decision between either fixing libexecinfo or removing it:
https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/36722
They chose the latter as they felt it wasn't useful for the end user and there was no loss of functionality vs staying with the broken libexeinfo.
https://gitlab.alpinelinux.org/alpine/aports/-/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
There is also a supposedly fixed version libexecinfo using libelf here:
https://git.ddd.rip/psykose/libexecinfo
The downside of using this implementation is that the abi is different meaning that all applications using libexecinfo will need to be recompiled. I also haven't tested it, so I can't confirm how well it works or if there are other considerations.
next reply other threads:[~2022-12-18 5:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 5:23 oreo639 [this message]
2022-12-18 6:47 ` nekopsykose
2022-12-18 6:47 ` nekopsykose
2022-12-18 6:48 ` nekopsykose
2022-12-18 6:53 ` nekopsykose
2022-12-18 6:54 ` nekopsykose
2022-12-18 6:59 ` nekopsykose
2022-12-18 7:16 ` nekopsykose
2022-12-18 8:41 ` oreo639
2022-12-18 8:43 ` oreo639
2022-12-18 8:43 ` oreo639
2022-12-18 8:44 ` oreo639
2022-12-18 8:45 ` oreo639
2022-12-18 8:45 ` oreo639
2022-12-18 8:48 ` oreo639
2022-12-18 8:49 ` oreo639
2022-12-18 8:50 ` oreo639
2022-12-18 8:53 ` oreo639
2022-12-18 8:54 ` nekopsykose
2022-12-18 8:54 ` oreo639
2022-12-18 8:54 ` nekopsykose
2022-12-18 8:55 ` nekopsykose
2022-12-18 8:55 ` oreo639
2022-12-18 9:41 ` oreo639
2022-12-18 9:49 ` oreo639
2022-12-18 9:50 ` oreo639
2022-12-18 9:50 ` oreo639
2022-12-18 9:50 ` oreo639
2022-12-18 9:51 ` oreo639
2022-12-18 9:52 ` oreo639
2022-12-18 9:53 ` oreo639
2022-12-18 9:54 ` oreo639
2022-12-18 9:59 ` oreo639
2022-12-18 10:17 ` nekopsykose
2023-03-19 2:02 ` github-actions
2023-03-19 2:18 ` oreo639
2023-03-19 3:06 ` nekopsykose
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-41159@inbox.vuxu.org \
--to=oreo639@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).