RFR: 8340334: Update jcmd VM.events max parameter to be INT
Leonid Mesnik
lmesnik at openjdk.org
Tue Nov 19 00:45:25 UTC 2024
The jcmd VM.events max parameter type is changed to INT.
Also,I noted the max <= 0 is ignored, so I updated documentation and set "0" as a default value.
The jcmd exists if parameter is negative now.
The `max` is `int` while really it is the unsigned int. However I don't think it makes sense to change it to `size_t` or `unsigned int` in all places where 'max' is used.
-------------
Commit messages:
- max_value -> max
- parameter changed to log
Changes: https://git.openjdk.org/jdk/pull/22224/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22224&range=00
Issue: https://bugs.openjdk.org/browse/JDK-8340334
Stats: 10 lines in 2 files changed: 0 ins; 4 del; 6 mod
Patch: https://git.openjdk.org/jdk/pull/22224.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/22224/head:pull/22224
PR: https://git.openjdk.org/jdk/pull/22224
More information about the serviceability-dev
mailing list