-
Bug
-
Resolution: Fixed
-
P4
-
8, 11, 17, 18, 19
-
b08
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8284171 | 17.0.4 | Thomas Stuefe | P4 | Resolved | Fixed | b01 |
| JDK-8317303 | 11.0.22 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
Sonarcloud told me that in `DCmdArgument<jlong>::parse_value()`, we explicitly handle NULL input strings for the parse value, then print it out as part of the assembled exception message.
I don't think this can ever happen IRL, it is theoretical only. But we should fix it nevertheless. It also can be simplified, I don't think the temporary string copy is needed.
I don't think this can ever happen IRL, it is theoretical only. But we should fix it nevertheless. It also can be simplified, I don't think the temporary string copy is needed.
- backported by
-
JDK-8284171 DCmdArgument<jlong>::parse_value() should handle NULL input
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk11u-dev/0beae376
-
Commit
openjdk/jdk17u-dev/0bb751bf
-
Commit
openjdk/jdk/55f180fb
-
Review
openjdk/jdk11u-dev/2153
-
Review
openjdk/jdk17u-dev/325
-
Review
openjdk/jdk/7079
(3 links to)