Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] libexecinfo broken on musl
Date: Sun, 18 Dec 2022 10:51:24 +0100	[thread overview]
Message-ID: <20221218095124.F-H8ik9iRt1CxNHwgiwPO4uSLGiFW8C3aEbSM2_TVK8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41159@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/41159#issuecomment-1356738883

Comment:
Thank your so much for the clarifications.

> the entire ABI is just the backtrace functions. if you mean the SONAME, that can freely be made to match. (i.e., there is no recompiling needed). (..maybe there was a stray other symbol? i remember seeing one, but nothing ever calls it in practice so an empty stub could be added)

Yeah, my bad.
When I was testing it with compiling ldc (libexecinfo is used by llvm12) I got:
```
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_strptr: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: gelf_getehdr: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_begin: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: gelf_getsym: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_nextscn: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_getdata: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_version: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_end: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: gelf_getshdr: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_errmsg: symbol not found
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_errno: symbol not found
```
At the time I assumed that some function that used to be provided isn't being provided anymore, but yeah, that's definitely a different issue.

> well.. it doesn't segfault, that's about all i can really say for it. it's a port of the latest version of libexecinfo from freebsd, which happens to have moved to libelf since the last one that was used (also a port)

To be clear, what I meant by that was that I haven't really tested it due to the above issue.

> i never found a point to have libexecinfo backtrace()

Fair.
It is currently required by LLVM for GWP-ASan. I personally had never used it (or heard of it) before looking into said issue.
~~That being said. I tried to use it with an intentional use-after-free which, for me, resulted in nothing happening. (with the current libexecinfo)~~
Edit: I do get the infinite loop in GWP-ASan.

> on top of that, i'm not sure how well that backtrace works with `-fomit-frame-pointer -O2` on an executable

I don't think we use `-fomit-frame-pointer`, correct me if I am wrong.

  parent reply	other threads:[~2022-12-18  9:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18  5:23 [ISSUE] " oreo639
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 [this message]
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=20221218095124.F-H8ik9iRt1CxNHwgiwPO4uSLGiFW8C3aEbSM2_TVK8@z \
    --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).