-
Enhancement
-
Resolution: Fixed
-
P4
-
20
-
b10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8344616 | 17.0.14 | Goetz Lindenmaier | P4 | Resolved | Fixed | b05 |
| JDK-8333719 | 17.0.13-oracle | Mimoun Ghordou | P4 | Resolved | Fixed | b01 |
There are multiple ways which the stack guard pages tests can be hardened:
- [~iklam] suggested rewriting the Java part of the test using ProcessTools.executeProcess(ProcessBuilder pb) which will make stdout/stderr be consistently logged and debugging much easier.
- Split up initial/other thread into 2 tests
- Split up Java thread tests and native thread tests into two separate files
This will help us withJDK-8293452
- [~iklam] suggested rewriting the Java part of the test using ProcessTools.executeProcess(ProcessBuilder pb) which will make stdout/stderr be consistently logged and debugging much easier.
- Split up initial/other thread into 2 tests
- Split up Java thread tests and native thread tests into two separate files
This will help us with
- backported by
-
JDK-8333719 Harden runtime/StackGuardPages/TestStackGuardPages.java
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8293452 runtime/StackGuardPages/TestStackGuardPages.java "Test FAILED. Stack guard page is still there at NNNNN"
-
- Closed
-
- links to
-
Commit
openjdk/jdk/8c2c8b3f
-
Commit(master)
openjdk/jdk17u-dev/a49d5eaf
-
Review
openjdk/jdk/12386
-
Review(master)
openjdk/jdk17u-dev/3051
(2 links to)