From: Carlos O'Donell <carlos@redhat.com>
To: "Gabriel F. T. Gomes" <gabriel@inconstante.net.br>
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: Fri, 27 Dec 2019 12:13:00 -0000 [thread overview]
Message-ID: <a99573a9-8b77-bf33-d035-0bfac5e23797@redhat.com> (raw)
In-Reply-To: <20191226172138.5a6a4151@tereshkova>
On 12/26/19 3:21 PM, Gabriel F. T. Gomes wrote:
> 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.
Did you try --enable-hardcoded-path-in-tests?
>> 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.
>
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-12-27 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 21:20 Carlos O'Donell
2019-12-26 20:21 ` Gabriel F. T. Gomes
2019-12-27 12:13 ` Carlos O'Donell [this message]
2019-12-27 17:56 ` Gabriel F. T. Gomes
2020-01-04 14:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a99573a9-8b77-bf33-d035-0bfac5e23797@redhat.com \
--to=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=gabriel@inconstante.net.br \
--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