Open dusanboskovic opened 4 years ago
I had to dig through a lot of internal history to find the purpose of that tracepoint.
The purpose is to capture the raw bytes from a class before it's defined using a command like:
java -Xtrace:none -Xtrace:maximal={j9bcu.198,j9bcu.1},output=c:\170\boo -version
It's defined at level 7 as it shouldn't be enabled by default. Unfortunately, trying to make it more readable would make it less useful for the above purpose.
What brought it to your attention?
My preference would be to remove this tracepoint in the future and replace it with a new -Xdump:classbytes
option to allow capturing classes at the defineClass call
What Dusan suggests would have no effect on the example above using output=...
.
People use the command traceformat c:\170\boo
and then examine c:\170\boo.fmt
. It's not helpful that a lot of information has been erased as c:\170\boo.fmt
is produced. As I understand it, he's asking that there is a way to avoid that erasure.
The Trc_BCU_internalDefineClass_FullData tracepoint should output data in a more human readable format, example below: