Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2177293 | 7 | Keith Mcguigan | P3 | Closed | Fixed | b39 |
JDK-2172802 | 6u14 | Keith Mcguigan | P3 | Closed | Fixed | b01 |
There's a regression in the argument parsing code
of the HotSpot which leads to a segmentation fault if an -XX option
with an empty string argument (e.g. -XX:SyncKnobs= or
-XX:SyncKnobs="") is given on the command line.
The regression must have appeared somewhere in HS 11, because Java
1.6.0_06 (which contains HS 10.0_b22) doesn't show the problem while
both Java 1.6.0_10 (HS 11.0_b11) and Java 1.7.0-ea-b24 (HS 12.0_b01)
as well as the latest OpenJDK snapshot (Rev. 292 with tag jdk7-b34)
are affected.
of the HotSpot which leads to a segmentation fault if an -XX option
with an empty string argument (e.g. -XX:SyncKnobs= or
-XX:SyncKnobs="") is given on the command line.
The regression must have appeared somewhere in HS 11, because Java
1.6.0_06 (which contains HS 10.0_b22) doesn't show the problem while
both Java 1.6.0_10 (HS 11.0_b11) and Java 1.7.0-ea-b24 (HS 12.0_b01)
as well as the latest OpenJDK snapshot (Rev. 292 with tag jdk7-b34)
are affected.
- backported by
-
JDK-2172802 HotSpot segfaults if given -XX options with an empty string argument
- Closed
-
JDK-2177293 HotSpot segfaults if given -XX options with an empty string argument
- Closed
- duplicates
-
JDK-6799458 java -XX:HeapDumpPath= fubar produces segmentation fault
- Closed
- relates to
-
JDK-6604006 globals.hpp should support non accumulating ccstr arguments
- Closed
-
JDK-6753795 HotSpot crash in strlen() when JVMTI is used
- Closed