Date: Fri, 17 Feb 2017 02:33:04 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 217138] head (e.g.) -r313783 sh vs. jemalloc asserts: include/jemalloc/internal/tsd.h:687: Failed assertion: "tsd_booted" Message-ID: <bug-217138-8-bXheSdFtW8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217138-8@https.bugs.freebsd.org/bugzilla/> References: <bug-217138-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217138 --- Comment #2 from Mark Millard <markmi@dsl-only.net> --- If one is going to look into this in a amd64 context it is important to be using head -r313772 or later in order to avoid fork sometimes not preserving the stack pointer on the child-process side of things --at least if experimenting with port or buildworld buildkernel builds as a means of testing. Getting past that stack pointer problem is what allowed me to see this problem during build activity, which started me down this exploration. [My tests for aborting in sh`forkshell if fork changes the stack pointer are still in place but there have been no failures so far.] -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217138-8-bXheSdFtW8>