public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alex_y_xu at yahoo dot ca" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29039] _dl_tlsdesc_dynamic (sometimes) returns garbage offsets
Date: Tue, 12 Apr 2022 15:18:31 +0000 [thread overview]
Message-ID: <bug-29039-131-KwB6qH3LAH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29039-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29039
--- Comment #2 from alex_y_xu at yahoo dot ca ---
(In reply to Florian Weimer from comment #1)
> Is there a way to get glibc debugging information on archlinux? I enabled
> debuginfod, and it downloaded some debugging information, but not for glibc.
>
> It looks like the fast path in _dl_tlsdesc_dynamic is taken, and I need to
> check what the data structures look like.
Thanks for looking into this!
As far as I know, Arch Linux currently doesn't have any public debug symbols
for the distro-packaged glibc. If you're more familiar with Ubuntu, that may be
preferable. It was originally reported on Ubuntu, but I had some issues
installing old Mesa packages on Ubuntu, whereas it is a single command on Arch.
I think Ubuntu has debug symbols for glibc though. If you'd like to continue
using Arch, following these steps should build and install a standard glibc
package with debug symbols:
sed -i -e '/^BUILDENV=/s/check/!check/' -e '/^OPTIONS=/s/!debug/debug/' -e
's/^#MAKEFLAGS="-j2"$/MAKEFLAGS="-j'$(nproc)'"' /etc/makepkg.conf
pacman -S base-devel asp sudo
sed -i -e 's/# %wheel ALL=(ALL:ALL) NOPASSWD: ALL/%wheel ALL=(ALL:ALL)
NOPASSWD: ALL/' /etc/sudoers
su - user
asp checkout glibc
cd glibc/trunk
gpg --recv-keys 16792B4EA25340F8
makepkg -si
I tested approximately this method and was able to reproduce the issue on bare
metal. Alternatively, it may be possible to manually install glibc with
./configure; make; make install. I didn't test this method; it may be necessary
to source /etc/makepkg.conf; export CFLAGS LDFLAGS in order to reproduce the
issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-12 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 5:36 [Bug dynamic-link/29039] New: " alex_y_xu at yahoo dot ca
2022-04-10 9:46 ` [Bug dynamic-link/29039] " evangelos at foutrelis dot com
2022-04-10 14:34 ` alex_y_xu at yahoo dot ca
2022-04-12 11:27 ` fweimer at redhat dot com
2022-04-12 15:18 ` alex_y_xu at yahoo dot ca [this message]
2022-05-17 20:20 ` j at bitron dot ch
2023-11-26 14:16 ` sam at gentoo dot org
2023-11-26 14:17 ` sam at gentoo dot org
2023-11-28 10:12 ` [Bug dynamic-link/29039] Corrupt DTV after reuse of a TLS module ID following dlclose with unused TLS fweimer at redhat dot com
2023-11-28 17:29 ` cvs-commit at gcc dot gnu.org
2023-12-20 8:46 ` cvs-commit at gcc dot gnu.org
2023-12-22 14:43 ` sam at gentoo dot org
2023-12-22 14:57 ` dilfridge at gentoo dot org
2023-12-22 16:58 ` cvs-commit at gcc dot gnu.org
2023-12-22 16:58 ` cvs-commit at gcc dot gnu.org
2023-12-22 16:59 ` cvs-commit at gcc dot gnu.org
2023-12-22 16:59 ` cvs-commit at gcc dot gnu.org
2023-12-22 17:00 ` cvs-commit at gcc dot gnu.org
2023-12-22 17:00 ` cvs-commit at gcc dot gnu.org
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=bug-29039-131-KwB6qH3LAH@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).