This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: test-in-container: Moving a test to a particular location *before* execution?
- From: Carlos O'Donell <carlos at redhat dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Tue, 10 Dec 2019 15:57:24 -0500
- Subject: Re: test-in-container: Moving a test to a particular location *before* execution?
- References: <xnd0cvuct3.fsf@greed.delorie.com>
On 12/10/19 3:48 PM, DJ Delorie wrote:
>
> I was thinking "would we ever need to run ld.so in the container
> anyway, and need that ld.so to be pid 1?"
>
> Like:
>
> /lib64/ld.so --some-flags tst-the-test.elf
>
> but I suppose you can still exec() ld.so from the test.
Oh! Yes. Yes we would. But running the loader itself is a weird
degenerate use case... thanks for thinking of that :-)
--
Cheers,
Carlos.