From owner-freebsd-current@freebsd.org Tue Aug 22 16:25:36 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6AB70DD1CC3 for ; Tue, 22 Aug 2017 16:25:36 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48FC06913F for ; Tue, 22 Aug 2017 16:25:36 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id 450A5DD1CC2; Tue, 22 Aug 2017 16:25:36 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4495ADD1CC0 for ; Tue, 22 Aug 2017 16:25:36 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C1096913E for ; Tue, 22 Aug 2017 16:25:35 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x231.google.com with SMTP id s187so25822021ywf.2 for ; Tue, 22 Aug 2017 09:25:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=jxiSeg13Nak5E1WfztG/Ex6oWmvgTvxzXoe+4q9EuR0=; b=nciR6+cJ/hWHQoEO2m6GEK1czA/5Bzgwc5PwCSwd6uW/BFb+uCeUNbKqPgN4WUhnjX 1GbZ91usXRJ3wdkttyohel7ZsRc5j3sKo5FUNxAGI+7Cu/Cazj/LoKKSBmyeQ5ap/85y rWSYZrRN+pW+PUxGUDdUSATAjTAxSHPQbtSrg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=jxiSeg13Nak5E1WfztG/Ex6oWmvgTvxzXoe+4q9EuR0=; b=r3lmWVyODslMQtpMkuF+rUMj1K8Vq30Oe5lDVEvrkfMyBEQJCeVOwI40473e0k/Qbv OqUbvS9Y1byc03PBtPey7lWAbZehSrN+tn4PC6Xq4NrjostSJ7Ppd6R811S+N5YhuDiQ 3FC4k5wb9BUxy6liyT38xl6ybRt4usRJHq3sB3XtSNhwZGiZguEZG1LFH4A7j9T9yT7Y rjQH+JGQVeHXBEPcTSYrocpHz6EtnHVpKtzWaBQp1BFXZGeTIv/O1PsMETFaCYbOTJks STIB/zENAwG3GHldBvoY1AQEr1OwiyNUmchDojU2J34hY7ztenL3xTwLduEoRiPGLSk8 GLwA== X-Gm-Message-State: AHYfb5gtjnO+tCbumxEU/5yylnW+adtIxQAukXIkyv7GdmaQDkY53ugP hWg5AqAmgbVsvIMYavV44ZByFXtBt4ce X-Received: by 10.37.73.131 with SMTP id w125mr1151928yba.324.1503419135015; Tue, 22 Aug 2017 09:25:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.57.21 with HTTP; Tue, 22 Aug 2017 09:25:04 -0700 (PDT) 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> From: Eitan Adler Date: Tue, 22 Aug 2017 12:25:04 -0400 Message-ID: Subject: Re: SIGSEGV in /bin/sh after r322740 -> r322776 update To: David Wolfskill , Konstantin Belousov , "current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Aug 2017 16:25:36 -0000 On 22 August 2017 at 09:38, David Wolfskill 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