Re: SIGSEGV in /bin/sh after r322740 -> r322776 update

From: Eitan Adler <lists_at_eitanadler.com>
Date: Tue, 22 Aug 2017 12:25:04 -0400
On 22 August 2017 at 09:38, David Wolfskill <david_at_catwhisker.org> wrote:
> On Tue, Aug 22, 2017 at 04:19:58PM +0300, Konstantin Belousov wrote:
>> ...
>> > > Ok, can you rebuild kernel and libc from scratch ?  I.e. remove your
>> > > object directories.
>> >
>> > I think I'll need a working /bin/sh to do that.  As noted, I could
>> > try the stable/11 /bin/sh; on the other hand, if it's dying in a
>> > library, that's not likely to help a whole lot. :-}
>> I highly suspect that this is not /bin/sh at all.  Backtrace strongly
>> suggests that the malloc() has issues, but again I suspect that the
>> reason is not an issue in malloc, but its use of TLS.
>
> I think I hope that this use of "TLS" is not the one associated with
> (say) SSL....  :-}

https://en.wikipedia.org/wiki/Thread-local_storage
Received on Tue Aug 22 2017 - 14:25:36 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:12 UTC