From nobody Thu Nov 13 14:41:49 2025
X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4d6jcX2y8Sz6Gy2C;
	Thu, 13 Nov 2025 14:40:44 +0000 (UTC)
	(envelope-from fbsd@www.zefox.net)
Received: from www.zefox.net (www.zefox.net [50.1.20.27])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4d6jcW728Fz3Nv2;
	Thu, 13 Nov 2025 14:40:43 +0000 (UTC)
	(envelope-from fbsd@www.zefox.net)
Authentication-Results: mx1.freebsd.org;
	none
Received: from www.zefox.net (localhost [127.0.0.1])
	by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 5ADEfn0C032888
	(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO);
	Thu, 13 Nov 2025 06:41:49 -0800 (PST)
	(envelope-from fbsd@www.zefox.net)
Received: (from fbsd@localhost)
	by www.zefox.net (8.18.1/8.18.1/Submit) id 5ADEfnQe032887;
	Thu, 13 Nov 2025 06:41:49 -0800 (PST)
	(envelope-from fbsd)
Date: Thu, 13 Nov 2025 06:41:49 -0800
From: bob prohaska <fbsd@www.zefox.net>
To: Carl Shapiro <cshapiro@panix.com>
Cc: Ronald Klop <ronald@freebsd.org>, freebsd-arm@freebsd.org,
        freebsd-current@freebsd.org
Subject: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld
Message-ID: <aRXuLTN4hkGykHIl@www.zefox.net>
References: <aOu7s9roGCofdCOw@www.zefox.net>
 <aOvTG-20QRJtJJwf@int21h>
 <CANCZdfrJ8rph_rkT3Mk-sNYKNspoV15SvHWLsahzS0HnULi4ww@mail.gmail.com>
 <aO068RrAehdiHOoZ@www.zefox.net>
 <aRUJPryA4Vmu8dDD@www.zefox.net>
 <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org>
 <87ldkai9lu.fsf@panix.com>
List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-current
List-Help: <mailto:freebsd-current+help@freebsd.org>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Subscribe: <mailto:freebsd-current+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-current+unsubscribe@freebsd.org>
Sender: owner-freebsd-current@FreeBSD.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87ldkai9lu.fsf@panix.com>
X-Spamd-Bar: ----
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Rspamd-Queue-Id: 4d6jcW728Fz3Nv2

On Thu, Nov 13, 2025 at 01:07:41AM -0800, Carl Shapiro wrote:
> Ronald Klop <ronald@FreeBSD.org> writes:
> 
> > My thought was triggered by this as a build of opendjk11 failed with a
> > jemalloc error.
> > https://lists.freebsd.org/archives/freebsd-pkg-fallout/2025-September/804963.html
> 
> Is this build failure very reproducible?  Is there more of a stack trace
> to go with it?
> 
All the assertion failures I've seen have been in the clang libraries during
buildworld. They appear to happen in a variety of cases, indicated by the 
different .sh and .cpp filenames found in the files under
http://www.zefox.net/~fbsd/assertion_failure/

The failures are random in the sense that restarting buildworld either
produces a new assertion failure in a different library or completion.

It isn't obvious how to capture a stack trace, if you can provide guidance
I'll give it a try. As is, buildworld simply stops, the machine does not
crash. 

Thanks for writing!

bob prohaska