Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Unkown error occurred: Exception: System.NullReferenceException #58

Open
tigran-halatrian opened this issue Oct 30, 2019 · 2 comments

Comments

@tigran-halatrian
Copy link

[ERROR] Unknown error occurred.
Exception: System.NullReferenceException: link to object doesn't link to instance of the object
in Confuser.Renamer.Analyzers.LdtokenEnumAnalyzer.Analyze(ConfuserContext context, INameService service, ProtectionParameters parameters, IDnlibDef def) in G:\Users\Xenocode\Source\Repos\neo-ConfuserEx\Confuser.Renamer\Analyzers\LdtokenEnumAnalyzer.cs:line55
in Confuser.Renamer.AnalyzePhase.Analyze(NameService service, ConfuserContext context, ProtectionParameters parameters, IDnlibDef def, Boolean runAnalyzer) in G:\Users\Xenocode\Source\Repos\neo-ConfuserEx\Confuser.Renamer\AnalyzePhase.cs:line 133
in Confuser.Renamer.AnalyzePhase.Execute(ConfuserContext context, ProtectionParameters parameters) in G:\Users\Xenocode\Source\Repos\neo-ConfuserEx\Confuser.Renamer\AnalyzePhase.cs:line 55
in Confuser.Core.ProtectionPipeline.ExecuteStage(PipelineStage stage, Action1 func, Func1 targets, ConfuserContext context) in G:\Users\Xenocode\Source\Repos\neo-ConfuserEx\Confuser.Core\ProtectionPipeline.cs:line 138
in Confuser.Core.ConfuserEngine.RunPipeline(ProtectionPipeline pipeline, ConfuserContext context) in G:\Users\Xenocode\Source\Repos\neo-ConfuserEx\Confuser.Core\ConfuserEngine.cs:line 219
in Confuser.Core.ConfuserEngine.RunInternal(ConfuserParameters parameters, CancellationToken token) in G:\Users\Xenocode\Source\Repos\neo-ConfuserEx\Confuser.Core\ConfuserEngine.cs:line 173
Failed at 20:37, 0:00 elapsed.

@tigran-halatrian
Copy link
Author

This is a low priority one. As it seems most probably already obfuscated dll was used as an input.

@init5-SF
Copy link

init5-SF commented Apr 2, 2021

I have the same issue, and no the input was not already obfuscated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants