From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: glibc: restore debug symbols
Date: Tue, 13 Apr 2021 21:36:19 +0200 [thread overview]
Message-ID: <20210413193619.CJXJ9H1tGJeuX5CP1pcIuCDUyPPYbCReaUwYDkZd2oE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30216@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/30216#issuecomment-819001345
Comment:
> I'm not sure what this fixes; `nostrip_files` should only mean that the debug symbols are kept in the shared libraries themselves instead of in a separate file under `/usr/debug`.
Indeed. I was debugging an issue on glibc-2.33 and symbols were unresolvable for some reason (it must have been a stale glibc from a non-debug build of mine). I just checked on a fresh base-voidstrap from the official repos, it seems to be working fine.
Sorry for the noise, I'll close this one.
next prev parent reply other threads:[~2021-04-13 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 18:42 [PR PATCH] " ailiop-git
2021-04-13 18:45 ` ericonr
2021-04-13 19:36 ` ailiop-git [this message]
2021-04-13 19:37 ` [PR PATCH] [Closed]: " ailiop-git
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=20210413193619.CJXJ9H1tGJeuX5CP1pcIuCDUyPPYbCReaUwYDkZd2oE@z \
--to=ailiop-git@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).