This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Question about tst-stack4


I have a question about nptl/tst-stack4.  In the 2.25 release notes,
this shows up as a failure on a number of platforms.  One references a
defect report (https://sourceware.org/bugzilla/show_bug.cgi?id=19329)
and the others all reference a glibc checkin that caused the failure:

commit 17af5da98cd2c9ec958421ae2108f877e0945451
Author: Alexandre Oliva <aoliva@redhat.com>
Date:   Wed Sep 21 22:01:16 2016 -0300

    [PR19826] fix non-LE TLS in static programs


In the 2.26 release notes the platforms where it fails all just
mention a timeout.

Currently, with top-of-tree sources this test fails for me on
aarch64 with the new ILP32 ABI but passes with the LP64 ABI.
The failure I see in nptl/tst-stack4.out is:

Didn't expect signal from child: got `Segmentation fault'

Is this the error that the other failing platforms are seeing?
(ARM, Microblaze, MIPS, Nios II, PowerPC [32 bit soft-float])

Are there any other platforms that are getting a Segfault?
Given how often this shows up in other platforms failing list,
I am not sure if there is a aarch64 ILP32 specific issue here 
or a more generic bug that has been around for a while.

Steve Ellcey
sellcey@cavium.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]