Print disassembly of generated bytecode

[FroMage]

Writing an extension that generates bytecode with ASM or gizmo pretty often you get things wrong and have verify errors or just buggy generated code. It would be really nice if there were an option to make shamrock generate disassembled bytecode of what we just generated.

[geoand]

Are you thinking about some kind of integration with https://github.com/fesh0r/fernflower?

[stuartwdouglas]

JClasslib is really good for this. Its not disassembled, but rather lets you look at the raw bytecode you have generated in an easy to understand way.

[FroMage]

JClasslib requires me to open that tool and set it up. I'd really love if I could set this property:

shamrock.log.bytecode-magic=true
shamrock.log.bytecode-magic.packages=io.stef.model

And have the generated classes in io.stef.model dumped on STDERR, disassembled. Or dumped to target/generated-sources or other. Actually even dumped on STDERR as bytecode would be a lot of help :)

[dmlloyd]

I like this idea, having spent quite a lot of time dealing with generated code in the last few weeks.

It would be great if we could generate a fake "source" file that contains the bytecode generated plus some notation which includes the stack trace element of the line of code that generated that section of bytecode. The generated text file could then be set as the source file of the generated .class file, with line number tables that match up with the text, so that you can step through it in a debugger.

[dmlloyd]

Doing this via config should definitely be possible using the new code.

[stuartwdouglas]

Will the dissembler actually work on invalid bytecode?

[dmlloyd]

I think IDEA will reference any source file regardless of language (or lack there of), as long as it's the same file referenced in the bytecode and the file is in the right package on a source path (or in this case, generated source path).