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> In-Reply-To: <87ldkai9lu.fsf@panix.com> 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>
index | next in thread | previous in thread | raw e-mail
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 prohaskahelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aRXuLTN4hkGykHIl>