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: Fri, 27 Dec 2019 14:55:51 -0300 [thread overview]
Message-ID: <20191227145551.79a291b4@tereshkova> (raw)
In-Reply-To: <a99573a9-8b77-bf33-d035-0bfac5e23797@redhat.com>
Hi, Carlos,
On Fri, 27 Dec 2019, Carlos O'Donell wrote:
>
>Did you try --enable-hardcoded-path-in-tests?
I hadn't. ¬¬
That was it.
You wrote this in your first email:
>In test-container.c we mount $srcdir and $objdir into the same absolute paths
>inside the container, so ld.so should be accessible from the same absolute paths.
>If we fail those mounts we immediately fail the test with FAIL_EXIT1.
I think the paths are the same, but the contents are not identical. On
the tests I did, the testroot.root/path/to/build/dir/elf directory is
missing the symlink between ld.so and ld<whatever>.so.<n>. For instance:
$ ls -l testroot.root/home/gabriel/build/x86_64/glibc/elf
-rwxrwxr-x 1 gabriel gabriel 1342800 Dec 27 11:09 ld-linux-x86-64.so.2
$ ls -l testroot.root/home/gabriel/build/powerpc64le/glibc/elf/
-rwxr-xr-x 1 gabriel gabriel 1566232 Dec 27 09:05 ld64.so.2
Whereas on the actual build dir:
$ ls -l elf/ld*.so*
lrwxrwxrwx 1 gabriel gabriel 5 Dec 27 09:04 elf/ld64.so.2 -> ld.so
-rwxr-xr-x 1 gabriel gabriel 1566232 Dec 27 09:04 elf/ld.so
>warning: Could not load shared library symbols for /home/carlos/build/glibc-gr-localedef/elf/ld.so.
If I create the ld.so symlink in the sysroot, the problem goes away.
Should there be a symlink in the sysroot?
next prev parent reply other threads:[~2019-12-27 17:56 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
2019-12-27 12:13 ` Carlos O'Donell
2019-12-27 17:55 ` Gabriel F. T. Gomes [this message]
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=20191227145551.79a291b4@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).