-
Bug
-
Resolution: Fixed
-
P5
-
None
-
b12
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8343690 | 21.0.7-oracle | Yagmur Eren | P5 | Resolved | Fixed | master |
JDK-8329505 | 21.0.4 | Aleksey Shipilev | P5 | Resolved | Fixed | b01 |
JDK-8343691 | 17.0.15-oracle | Yagmur Eren | P5 | Resolved | Fixed | master |
JDK-8345711 | 17.0.15 | Goetz Lindenmaier | P5 | Resolved | Fixed | master |
lists 'path-to-gc-root' option, however, the actual option name is 'path-to-gc-roots'
The same holds for JFR.stop documentation. Also, in the examples to JFR.dump command, there is a line with two typos:
$ jcmd <pid> JFR.dump fillename=leaks.jfr path-to-gc-root=true
Note "fillename" and "path-to-gc-root".
The manual page for "jcmd" (man jcmd) also mentions 'path-to-gc-root' instead of 'path-to-gc-roots'
- backported by
-
JDK-8329505 jcmd: typo in the documentation of JFR.start and JFR.dump
- Resolved
-
JDK-8343690 jcmd: typo in the documentation of JFR.start and JFR.dump
- Resolved
-
JDK-8343691 jcmd: typo in the documentation of JFR.start and JFR.dump
- Resolved
-
JDK-8345711 jcmd: typo in the documentation of JFR.start and JFR.dump
- Resolved
- links to
-
Commit openjdk/jdk21u-dev/4c7b1d93
-
Commit openjdk/jdk/16d917a8
-
Commit(master) openjdk/jdk17u-dev/b90bb122
-
Review openjdk/jdk21u-dev/410
-
Review openjdk/jdk/16413
-
Review(master) openjdk/jdk17u-dev/3088