You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into problems on an obfuscated jar. The essential code is as follows:
interface A {
B a();
C a();
};
abstract class B implements A {
@Override
C a() { ... } ;
};
class C extends A {
@Override
B a() { ... };
};
Deobfuscation renames the first a method, but class B ends up with the wrong alias. This also happens if the renaming is done manually.
interface A {
B xxx();
C a();
};
abstract class B implements A {
C xxx() { ... } ;
};
class C extends B {
B a() { ... };
};
I suspect this is due to overly lax (name based instead of prototype based?) identification of MethodNodes or MethodInfo objects. Also not too sure how easy it would be to triage and fix, so submitted as a feature request
The text was updated successfully, but these errors were encountered:
I ran into problems on an obfuscated jar. The essential code is as follows:
Deobfuscation renames the first
a
method, but class B ends up with the wrong alias. This also happens if the renaming is done manually.I suspect this is due to overly lax (name based instead of prototype based?) identification of
MethodNodes
orMethodInfo
objects. Also not too sure how easy it would be to triage and fix, so submitted as a feature requestThe text was updated successfully, but these errors were encountered: