Date: Thu, 13 Nov 2025 01:07:41 -0800 From: Carl Shapiro <cshapiro@panix.com> To: Ronald Klop <ronald@FreeBSD.org> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Message-ID: <87ldkai9lu.fsf@panix.com> In-Reply-To: <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> (Ronald Klop's message of "Thu, 13 Nov 2025 09:11:51 %2B0100") 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>
index | next in thread | previous in thread | raw e-mail
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? 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/1224home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87ldkai9lu.fsf>