Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld
- Reply: Ronald Klop : "Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld"
- Reply: bob prohaska : "Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld"
- In reply to: Ronald Klop : "Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 13 Nov 2025 09:07:41 UTC
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/1224