From owner-freebsd-bugs@freebsd.org  Fri Feb 24 03:28:36 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 1972CCEAC1A
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 24 Feb 2017 03:28:36 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0864210D7
 for <freebsd-bugs@FreeBSD.org>; Fri, 24 Feb 2017 03:28:36 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1O3SZvC030081
 for <freebsd-bugs@FreeBSD.org>; Fri, 24 Feb 2017 03:28:35 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 217239] head (e.g.:) -r313864 arm64 vs. jemalloc without
 MALLOC_PRODUCTION: various examples of tbin->avail being zero lead to
 SIGSEGV's
Date: Fri, 24 Feb 2017 03:28:36 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: markmi@dsl-only.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217239-8-05U69CmRDq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217239-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-217239-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:28:36 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217239

--- Comment #7 from Mark Millard <markmi@dsl-only.net> ---
(In reply to Mark Millard from comment #6)

A note on script failures:

I'll note that such script failures are
part of the overall activity reported
in bugzilla 217138. 217138's report is
biased to the sh failures, in part
because they happen first. But script
is involved.

--=20
You are receiving this mail because:
You are the assignee for the bug.=