On Tue, 6 Jan 2026 11:50:30 GMT, Kevin Walls <[email protected]> wrote:
> "VM.classes -verbose" is _very_ verbose already, so a separate option looks > like the right choice to me. More lightweight queries for just this info. > > $ build/linux-x64/images/jdk/bin/jcmd 741576 VM.classes | wc -l 544 $ > build/linux-x64/images/jdk/bin/jcmd 741576 VM.classes -verbose | wc -l 18209 > (on a trivial test app) given the verbosity, its my inclination is to leave the impl as it is, with a distinct option flag for location, perhaps also adding it (location) if -verbose is specified (instead) ... for completeness. until such time as all jcmds support "human readable", & "machine parseable" formatting options I think that the small incremental effort required to maintain an albeit informal (and unsupported) contract here is worth it in the interim, I for one have no insight into what extent jcmd users depend on the current (plain text) formats as parseable but would prefer to avoid breaking any such assumptions for the price of an option flag (in moderation of course) ------------- PR Comment: https://git.openjdk.org/jdk/pull/29048#issuecomment-3716463122
