-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b06
-
x86
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2205090 | 7 | Vladimir Kozlov | P3 | Closed | Fixed | b125 |
JDK-2205861 | 6u25 | Vladimir Kozlov | P3 | Resolved | Fixed | b01 |
StringBuffer should throw NPE when invoked with null however with -XX:+AggressiveOpts it substitute null instead.
Here is example.
class TSB {
public static void main (String[] args) {
while(true) {
System.out.println(stringmakerBUG());
}
}
public static String stringmakerBUG() {
try {
return new StringBuffer(null).toString();
} catch (NullPointerException e) {
return "NPE";
}
}
}
run:
java -server -XX:+AggressiveOpts TSB
Here is example.
class TSB {
public static void main (String[] args) {
while(true) {
System.out.println(stringmakerBUG());
}
}
public static String stringmakerBUG() {
try {
return new StringBuffer(null).toString();
} catch (NullPointerException e) {
return "NPE";
}
}
}
run:
java -server -XX:+AggressiveOpts TSB
- backported by
-
JDK-2205861 HS with -XX:+AggressiveOpts optimize new StringBuffer(null) so it does not throw NPE as expected
-
- Resolved
-
-
JDK-2205090 HS with -XX:+AggressiveOpts optimize new StringBuffer(null) so it does not throw NPE as expected
-
- Closed
-