[Bug 236686] BSD grep causes openjdk11 configuration failures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236686 --- Comment #6 from ktulla...@gmail.com --- Well, temporarely swapping in a link to the gnu binary in /usr/bin, like a madman, did the trick. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 236686] BSD grep causes openjdk11 configuration failures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236686 ktulla...@gmail.com changed: What|Removed |Added CC||ktulla...@gmail.com --- Comme

[Bug 239894] security.bsd.stack_guard_page default causes Java to crash

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894 --- Comment #6 from Greg Lewis --- Hi Konstantin, I think my explanation hasn't been clear enough. So let me try and include a few more links and some diagrams. Here is a diagram for what the Java thread stack looks like from https://git

[Bug 239997] Add environment variable to unbreak iocage upgrades

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239997 Xin LI changed: What|Removed |Added CC||delp...@freebsd.org --- Comment #1 from X

Search Engine Optimization Tips

June 2019 - SEO News & Tips Hi Guys, We all need to direct traffic to our websites. And not only direct existing customers to our websites but new potential customers as well. In this email I would like to introduce to you an amazing 205 point ultimate S.E.O strategy. 1. Myth of the Aging

[Bug 239894] security.bsd.stack_guard_page default causes Java to crash

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894 --- Comment #5 from Konstantin Belousov --- (In reply to Greg Lewis from comment #3) I am not proposing to interpret any SIGSEGV as a stack overflow. I propose to consider a SIGSEGV as the stack overflow if it occured in the range of [guar

[Bug 239894] security.bsd.stack_guard_page default causes Java to crash

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894 --- Comment #4 from Kurt Miller --- 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' mea

[Bug 239894] security.bsd.stack_guard_page default causes Java to crash

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894 --- Comment #3 from Greg Lewis --- Thanks for the response Konstantin! I can see a couple of problems with that approach. The biggest problem is that not all SIGSEGV should be interpreted as a stack overflow. With the possibility of what

[Bug 239997] Add environment variable to unbreak iocage upgrades

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239997 Bug ID: 239997 Summary: Add environment variable to unbreak iocage upgrades Product: Base System Version: CURRENT Hardware: Any URL: https://github.com/iocage/iocage/pull/

[Bug 239977] Integer Overflow: ping(8) option "-G" and "-g", bypass the invalid sweepmax and sweepmin packet size check

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239977 Kubilay Kocak changed: What|Removed |Added Severity|Affects Many People |Affects Some People F

[Bug 239978] Integer Overflow: ping(8) option "-h", bypass the invalid sweepincr packet size check

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239978 Kubilay Kocak changed: What|Removed |Added Keywords|patch |easy, needs-qa Severity|

[Bug 239976] Integer Overflow: ping(8) option "-s", bypass the invalid packet size check

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239976 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable11?, |

[Bug 239976] Integer Overflow: ping(8) option "-s", bypass the invalid packet size check

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239976 Kubilay Kocak changed: What|Removed |Added CC||sect...@freebsd.org St

[Bug 239894] security.bsd.stack_guard_page default causes Java to crash

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894 --- Comment #2 from Konstantin Belousov --- (In reply to Greg Lewis from comment #0) Can you switch from checking that the faulted address belong strongly to the guard pages created explicitly, to the mere fact that the faulted address fall