This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Status of build bots?
* Szabolcs Nagy:
> On 22/08/2019 12:21, Florian Weimer wrote:
>> * Szabolcs Nagy:
>>
>>> i do look at the aarch64 and armhf build bots, but i
>>> was away on holiday for a week.
>>>
>>> (aarch64 buildbot is supposed to be green, except for
>>> occasional FAIL: malloc/tst-malloc-thread-exit, same as
>>> https://sourceware.org/bugzilla/show_bug.cgi?id=24537
>>> i might move that test to xtest too. armhf unfortunately
>>> suffers from an arm64 kernel bug that applies aarch64
>>> signal stack limits to aarch32 processes, it should be
>>> fixed in new kernels but i cannot update that machine)
>>>
>>> now i see
>>>
>>> FAIL: elf/tst-dlopen-aout
>>> FAIL: elf/tst-dlopen-aout-container
>>>
>>> $ elf/ld-linux-aarch64.so.1 --library-path nptl:dlfcn:. elf/tst-dlopen-aout
>>> error: tst-dlopen-aout.c:48: dlopen succeeded unexpectedly: elf/tst-dlopen-aout
>>> error: 1 test failures
>>
>> Does the toolchain default to PIE? Does the link editor add the
>> DF_1_PIE flag to the main program?
>
> looks PIE with DF_1_PIE set:
Looks like it. So the dlopen succeeds because it doesn't load the
object, but somehow recognizes the previously loaded object.
I'll check if I can reproduce this behavior on aarch64.
Thanks,
Florian