This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Debugging containerized glibc tests with gdb (a developer use case for outside-of-container debugging).
- From: "Gabriel F. T. Gomes" <gabriel at inconstante dot net dot br>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: DJ Delorie <dj at redhat dot com>, libc-alpha <libc-alpha at sourceware dot org>, Gdb <gdb at sourceware dot org>, Gary Benson <gbenson at redhat dot com>, Florian Weimer <fweimer at redhat dot com>
- Date: Thu, 26 Dec 2019 17:21:38 -0300
- Subject: Re: Debugging containerized glibc tests with gdb (a developer use case for outside-of-container debugging).
- References: <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.