xxDark

Please try disabling `Use existing data` in assembler's config and see if that helps.

This option allows you to see local variable names, that's all iirc.

Revert exit stuff I changed for now, there are some hackery stuff happening here.

I'm rewriting a lot of parts of stack/locals implementation, right now you would need to make your own `ThreadStorage` and `Stack`/`Locals` implementation It would be better to implement verifier like...

Replying in case this is still relevant On [refactor branch](https://github.com/xxDark/SSVM/tree/refactor): ```Java VirtualMachine vm = new VirtualMachine(); vm.bootstrap(); ... JVMTIEnv env = vm.newJvmtiEnv(); env.setClassLink(klass -> { // verification process }); ......

Да без проблем, в основном твой лаунчер стоит на серверах с модами, найти уязвимость на выдачу предметов и записать нужные данные в нбт. Чем не способ? По поводу валидации: мне...

Ok, so, the first thing that I noticed is that the stack trace does not match with the sources. Seems like version 7.0.1 was released on November 2020, I'll try...

https://github.com/Guardsquare/proguard/blob/0344c58b3d43799ce203737eea3fd1b58ca701ad/base/src/proguard/optimize/evaluation/EvaluationShrinker.java#L1628 The error is caused by this line, looking at the list of opcodes, POP_X3 is the unsupported one. https://github.com/Guardsquare/proguard/blob/0344c58b3d43799ce203737eea3fd1b58ca701ad/base/src/proguard/optimize/evaluation/EvaluationShrinker.java#L1186 Also, as I may notice, newer version handles `MethodHandle.invoke*(..)` methods...

> Do you still get the same error regarding dup2_x1 with the latest version? Or a different error? Yes. > Could you compile ProGuard with DEBUG and DEBUG_RESULTS enabled in...

Is it possible to send the output somewhere else, i.e. not GitHub? E-mail, perhaps? Thanks.