This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Question about tst-stack4
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, libc-help at sourceware dot org
- Cc: nd at arm dot com, Steve Ellcey <sellcey at caviumnetworks dot com>
- Date: Thu, 17 Aug 2017 19:29:33 +0100
- Subject: Re: Question about tst-stack4
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Szabolcs dot Nagy at arm dot com;
- Nodisclaimer: True
- References: <1502831028.3962.208.camel@cavium.com> <53bf7be9-b339-fc62-7585-76312a5e5bad@linaro.org>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 16/08/17 14:08, Adhemerval Zanella wrote:
> On 15/08/2017 18:03, Steve Ellcey wrote:
>> 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'
>>
aarch64 dl-tlsdesc.S dynamic tlsdesc resolver has:
ldr PTR_REG (0), [x0] /* Load val member of DTV entry. */
cmp x0, #TLS_DTV_UNALLOCATED
b.eq 2f
can it be that the cmp against -1 goes wrong because
x0 is 32bit 0xffffffff ? then this would be returned
as the tls address here instead of initializing the
dtv entry.. do you see segfault at tls access with
address 0xffffffff?.