https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217138
--- Comment #2 from Mark Millard <mar...@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 on the CC list for the bug. _______________________________________________ freebsd-amd64@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
