Date: Tue, 22 Aug 2017 12:25:04 -0400 From: Eitan Adler <lists@eitanadler.com> To: David Wolfskill <david@catwhisker.org>, Konstantin Belousov <kostikbel@gmail.com>, "current@freebsd.org" <current@freebsd.org> Subject: Re: SIGSEGV in /bin/sh after r322740 -> r322776 update Message-ID: <CAF6rxgkvB0odoyQZn3G=2UEWA%2B%2BqvsQC5wrYiKT4Wgf3uxMGFQ@mail.gmail.com> In-Reply-To: <20170822133836.GQ1130@albert.catwhisker.org> References: <20170822114627.GC1130@albert.catwhisker.org> <20170822115923.GC1700@kib.kiev.ua> <20170822122836.GH1130@albert.catwhisker.org> <20170822123449.GD1700@kib.kiev.ua> <20170822124617.GN1130@albert.catwhisker.org> <20170822131958.GE1700@kib.kiev.ua> <20170822133836.GQ1130@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22 August 2017 at 09:38, David Wolfskill <david@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgkvB0odoyQZn3G=2UEWA%2B%2BqvsQC5wrYiKT4Wgf3uxMGFQ>