https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894
--- Comment #4 from Kurt Miller <k...@intricatesoftware.com> --- Yes, that's the root of the problem. The JVM needs to be able to deterministically manage its own guard pages independently from both the kernel placed ones and the pthread placed ones. Where 'manage' means change the protection of the pages to PROT_NONE and back to PROT_READ|PROT_WRITE. I think if the issues mentioned in comment #1 that kernel placed guard pages cause pthreads are corrected, it is very likely the JVM will be able to use the same method as libthr to place its guard pages (currently with mprotect(2)). -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
