From nobody Thu Nov 13 09:07:41 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 4d6ZDM5dQ9z6GXCc; Thu, 13 Nov 2025 09:07:47 +0000 (UTC) (envelope-from cshapiro@panix.com) Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4d6ZDL66lwz3PhC; Thu, 13 Nov 2025 09:07:46 +0000 (UTC) (envelope-from cshapiro@panix.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=panix.com header.s=panix header.b=aT2lrb9r; dmarc=pass (policy=none) header.from=panix.com; spf=pass (mx1.freebsd.org: domain of cshapiro@panix.com designates 166.84.1.89 as permitted sender) smtp.mailfrom=cshapiro@panix.com Received: from css-ThinkPad-T14s-Gen-2a (c-73-231-159-157.hsd1.ca.comcast.net [73.231.159.157]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4d6ZDL049Zz46TM; Thu, 13 Nov 2025 04:07:45 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1763024866; bh=l/c9MBifdDsOqnDr+SVsiL6A6AgAnW+88TrPy8e4RVs=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=aT2lrb9rSImhvec8nrCXbXnm7sxIL0uhMO5+2gxOQXprGUOc3Py+qrTqsBdw5Vc6p d5WDNHqnKkLLq8eJf9nT5KBgF7+nkQrRXAZ2Popu77siz6/GUl0PKMPvYMAkL5JLjR ozuBesgqARhnlIyFQeYfoZiz4W2UITGYaf8p+ZpU= From: Carl Shapiro To: Ronald Klop Cc: bob prohaska , freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld In-Reply-To: <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> (Ronald Klop's message of "Thu, 13 Nov 2025 09:11:51 +0100") References: <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> Date: Thu, 13 Nov 2025 01:07:41 -0800 Message-ID: <87ldkai9lu.fsf@panix.com> User-Agent: Gnus/5.13 (Gnus v5.13) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.14 / 15.00]; DWL_DNSWL_LOW(-1.00)[panix.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; NEURAL_HAM_MEDIUM(-0.94)[-0.945]; DMARC_POLICY_ALLOW(-0.50)[panix.com,none]; R_DKIM_ALLOW(-0.20)[panix.com:s=panix]; R_SPF_ALLOW(-0.20)[+ip4:166.84.1.64/26]; RCVD_IN_DNSWL_LOW(-0.10)[166.84.1.89:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[166.84.1.89:from]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DKIM_TRACE(0.00)[panix.com:+] X-Rspamd-Queue-Id: 4d6ZDL66lwz3PhC Ronald Klop 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? When the jemalloc witness code observes a locking error the process should abort immediately with a SIGABRT. However, there is SIGBUS reported in the build output prior to the witness error which makes it look like OpenJDK may have been handling a signal while the witness code was running. If malloc is somehow being called from a signal handler that is asking for trouble. Here's a closed issue from the old jemalloc repository about a witness error when malloc was called from a signal handler https://github.com/jemalloc/jemalloc/issues/1224