From: "Gabriel F. T. Gomes" <gabriel@inconstante.net.br>
To: Carlos O'Donell <carlos@redhat.com>
Cc: DJ Delorie <dj@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>, Gdb <gdb@sourceware.org>,
Gary Benson <gbenson@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: Debugging containerized glibc tests with gdb (a developer use case for outside-of-container debugging).
Date: Thu, 26 Dec 2019 17:21:38 -0300 [thread overview]
Message-ID: <20191226172138.5a6a4151@tereshkova> (raw)
In-Reply-To: <b0df7715-8506-4b90-d1ab-987309e967bb@redhat.com>
Hi, Carlos,
I tried this on several systems (varying archs and distros), but I wasn't
able to reproduce it (with elf/tst-ldconfig-bad-aux-cache)...
On Fri, 20 Dec 2019, Carlos O'Donell wrote:
>GNU gdb (GDB) Fedora 8.3-7.fc30
> [...]
>This GDB was configured as "x86_64-redhat-linux-gnu".
... even on Fedora 30 for x86_64, so I'm wondering if there's anything in
your configure options that I should try and mimic (I already tried some
combinations of --enable-profile --enable-addons --enable-multi-arch
--enable-tunables --enable-stack-protector=all, but I only tried that with
the system compiler (gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)).
>warning: Could not load shared library symbols for /home/carlos/build/glibc-gr-localedef/elf/ld.so.
I never got this.
>warning: Unable to find dynamic linker breakpoint function.
Nor this.
>warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable. Connect to gdbserver inside the container.
But this one, I got, too.
next prev parent reply other threads:[~2019-12-26 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 21:20 Debugging containerized glibc tests with gdb (a developer use case for outside-of-container debugging) Carlos O'Donell
2019-12-26 20:21 ` Gabriel F. T. Gomes [this message]
2019-12-27 12:13 ` Carlos O'Donell
2019-12-27 17:55 ` Gabriel F. T. Gomes
2020-01-04 14:28 ` Carlos O'Donell
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191226172138.5a6a4151@tereshkova \
--to=gabriel@inconstante.net.br \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=gbenson@redhat.com \
--cc=gdb@sourceware.org \
--cc=libc-alpha@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).