Github messages for voidlinux
 help / color / mirror / Atom feed
From: nekopsykose <nekopsykose@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] libexecinfo broken on musl
Date: Sun, 18 Dec 2022 09:54:58 +0100	[thread overview]
Message-ID: <20221218085458.AzEJKPudu04Ock0VdzQKR248R_gS3SEdnk4W-Jw_ir8@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: 1257 bytes --]

New comment by nekopsykose on void-packages repository

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

Comment:
```
Error relocating /usr/bin/../lib/../lib/libexecinfo.so.1: elf_strptr: symbol not found
```

that would be caused by a missing libelf.so not being found, as those are libelf symbols, no? there would be a failed to find message somewhere else in the output.  

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

it's the default on most(?) architectures for -O1 and higher. the manpage just says O1, but someone told me not everywhere- i'd have to look at the code to say for sure, but generally it's there anyway.  

> It is currently required by LLVM for GWP-ASan.  
ah.. right, that was the /single/ only thing i found that needed it for something non-generic :) i ended up merely disabling it for alpine.
i think q66 was working on getting that to work without execinfo, to get it working on chimera (also musl based and without libexecinfo).

> I tried to use it with an intentional use-after-free which, for me, resulted in nothing happening.  

most likely, it doesn't get anything via backtrace() so it gets no info to be useful due to the other issues here.


  parent reply	other threads:[~2022-12-18  8:54 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 [this message]
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=20221218085458.AzEJKPudu04Ock0VdzQKR248R_gS3SEdnk4W-Jw_ir8@z \
    --to=nekopsykose@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).