1<!--- 2Before creating a new issue, consider the following (this does not apply to 3feature requests): 4 5- if you need help on how to use ASM, please consult the documentation first 6(https://asm.ow2.io/documentation.html). If you can't find the answer there, 7describe your problem on the http://mail.ow2.org/wws/info/asm mailing listing 8instead of using GitLab issues. The mailing list has more subscribers than the 9GitLab issue tracker, and you will thus likely get a quicker answer via the 10mailing list. 11 12- check if your *input* classes are valid. For this you can use "javap -p -c -v 13<yourclass.class>". If this command fails, the bug is most likely in the tool 14that produced this class, not in ASM. Check the javap output carefully: 15sometimes the tool is able to print most of the class content, but fails to 16parse some part of it. In this case there can be an error message in the middle 17of the javap output, which can be easy to miss at first sight. 18 19- check if you are using the ASM API correctly. For this, insert one or more 20CheckClassAdapter instances in your class generation or class transformation 21chain (in particular, in front of ClassWriter instances). If a CheckClassAdapter 22throws an exception, this means that you are not using the ASM API correctly. 23Fix these issues first. 24 25If you still have a bug after completing the above steps, describe it below and 26make sure to provide detailed instructions on how to reproduce it. 27--> 28 29<!--- Provide a brief summary of the issue in the title above --> 30 31### Expected Behavior 32<!--- Tell us what should happen. --> 33 34### Current Behavior 35<!--- Tell us what happens instead of the expected behavior. --> 36 37### Steps to Reproduce 38<!--- 39Provide a self-contained example as an attached archive. If the source code to 40reproduce the issue is very small you can include it here directly (with its 41inputs, most likely some binary .class files, as an attached archive). 42--> 43