The debug agent has logging support that will trace all jdwp commands coming in. Currently all it traces is the command set number and the command number within that command set. So you see something like:
[#|10.01.2020 06:27:24.366 GMT|FINEST|J2SE1.5|jdwp|LOC=MISC:"debugLoop.c":240;;PID=12719;THR=t@915490560|:Command set 1, command 9|#]
It would be much better if it included the command set name and command name. For example:
[#|10.01.2020 06:27:24.366 GMT|FINEST|J2SE1.5|jdwp|LOC=MISC:"debugLoop.c":240;;PID=12719;THR=t@915490560|:Command set VirtualMachine(1), command Resume(9)|#]
In this example command set 1 represents VirtualMachine and the command 9 is the Resume command.
[#|10.01.2020 06:27:24.366 GMT|FINEST|J2SE1.5|jdwp|LOC=MISC:"debugLoop.c":240;;PID=12719;THR=t@915490560|:Command set 1, command 9|#]
It would be much better if it included the command set name and command name. For example:
[#|10.01.2020 06:27:24.366 GMT|FINEST|J2SE1.5|jdwp|LOC=MISC:"debugLoop.c":240;;PID=12719;THR=t@915490560|:Command set VirtualMachine(1), command Resume(9)|#]
In this example command set 1 represents VirtualMachine and the command 9 is the Resume command.
- relates to
-
JDK-8240142 Fix copyright in ThreadGroupReferenceImpl.h
-
- Resolved
-