StackMapGenerator debug output

[Michael van Acken]

Am Mi., 3. Aug. 2022 um 17:59 Uhr schrieb Adam Sotona <
adam.sotona at oracle.com>:

> StackMapGenerator is now providing more detailed info about root cause of
> the failure and appends bytecode print directly in the exception.
>
> All the critical information should be now visible in the provided
> exception message.
>
> Alternatively, a system variable switch can enable debug print, or it can
> be printed to a logger (which may cause issues with JDK bootstrap), or
> attached as another suppressed exception.
>

I just got a basic VerifyError without further information:

java.lang.VerifyError: Operand stack underflow
at
java.base/jdk.classfile.impl.StackMapGenerator$Frame.decStack(StackMapGenerator.java:1014)
at
java.base/jdk.classfile.impl.StackMapGenerator.processInvokeInstructions(StackMapGenerator.java:787)
at
java.base/jdk.classfile.impl.StackMapGenerator.processBlock(StackMapGenerator.java:624)
at
java.base/jdk.classfile.impl.StackMapGenerator.processMethod(StackMapGenerator.java:420)
at
java.base/jdk.classfile.impl.StackMapGenerator.generate(StackMapGenerator.java:293)
at
java.base/jdk.classfile.impl.StackMapGenerator.<init>(StackMapGenerator.java:232)
[...]

How can I activate the debug print you mention to get more information?

-- mva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/classfile-api-dev/attachments/20220804/bb63b7c4/attachment.htm>