-
Bug
-
Resolution: Fixed
-
P4
-
11, 17, 18
-
b24
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8277692 | 17.0.3-oracle | Thomas Stuefe | P4 | Resolved | Fixed | b01 |
JDK-8277476 | 17.0.2 | Thomas Stuefe | P4 | Resolved | Fixed | b06 |
JDK-8288366 | 11.0.17-oracle | Kevin Walls | P4 | Resolved | Fixed | b01 |
JDK-8277482 | 11.0.14 | Thomas Stuefe | P4 | Resolved | Fixed | b04 |
```
void jmm_GetDiagnosticCommandArgumentsInfo(JNIEnv *env,
jstring command, dcmdArgInfo* infoArray)
```
but array size is implicitly assumed to be known to both caller and callee. Caller and callee negotiate those sizes in prior steps, but things can go wrong. E.g. I recently hunted a bug where `DCmd::number_arguments()` was off - did not reflect the real number of its jcmd parameters - which led to a hidden memory overwriter.
Thankfully,
- backported by
-
JDK-8277476 JMM GetDiagnosticXXXInfo APIs should verify output array sizes
- Resolved
-
JDK-8277482 JMM GetDiagnosticXXXInfo APIs should verify output array sizes
- Resolved
-
JDK-8277692 JMM GetDiagnosticXXXInfo APIs should verify output array sizes
- Resolved
-
JDK-8288366 JMM GetDiagnosticXXXInfo APIs should verify output array sizes
- Resolved
- relates to
-
JDK-8264565 Templatize num_arguments() functions of DCmd subclasses
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/9b944096
-
Commit openjdk/jdk17u/0e896e7f
-
Commit openjdk/jdk/b8d33a2a
-
Review openjdk/jdk11u-dev/635
-
Review openjdk/jdk17u/276
-
Review openjdk/jdk/6363