search

SerenityEnterprises / paramorphism-issues

Issue board for Paramorphism JVM obfuscator
https://paramorphism.serenity.enterprises
6 stars 0 forks source link

ASM Throwing Method Too Large #10

Open Levelheader opened 5 years ago

Levelheader commented 5 years ago

I don't know for a fact if the obfuscator is the problem, or it's just me, but I have been obfuscated a specific jar with different versions. With b0.14 after Constant Indirection and Writing Classes ASM fails because of a method being too large. I haven't had this error before and I don't think any of my methods are too large. Is there a fix for this or is there something I don't know?

Levelheader commented 5 years ago

Ok I tested out some things and I figured out that b0.14 is less lenient about large methods. Methods that didn't cause problems in earlier versions now come out of the woodwork. I've fixed those methods and split them up and now this part of the obfuscation works.

char commented 5 years ago

Hm. Do you have any methods that are close to the max instruction count? (65535) The only thing I can see that would actually inflate the instructions that much would be the control flow obfuscation strategies - Goto Confusion & Jump Table Injection.

ccarpenter04 commented 4 years ago

Did you ever address this? I can generate a method that's close but not quite there.

Fohlen commented 4 years ago

This is the standard error that appears in malformed invokedynamic calls. I can't seem to find a reference, but I remember this error well.