The Dotfuscator Translator in the Config Editor translates obfuscated stack traces back to their original type and member names using the renaming map file generated during the protection process.
Use this tool when troubleshooting exceptions reported from a protected application.
Note: The Dotfuscator Translator requires the renaming map file generated for the same build as the protected application.
Before You Begin
Before decoding a stack trace, ensure you have:
- The obfuscated stack trace.
- The corresponding Dotfuscator renaming map file.
The map file must match the version of the application that produced the stack trace.
Open the Tool
- Open the Config Editor.
- From the Tools menu, select Decode Obfuscated Stack Trace.
The Dotfuscator Translator opens with two tabs:
| Tab | Description |
| Translate Lines | Translates an entire stack trace. |
| Translate Specific Element | Looks up individual types or methods. |
Translate an Obfuscated Stack Trace
To decode an entire stack trace:
- Select the renaming Map File.
- Paste the obfuscated stack trace into the input pane of the Translate Lines tab.
- Select Translate.
- Review the translated stack trace in the Translation Report section.
Translate a Specific Type or Method
If you need to identify a single obfuscated symbol rather than an entire stack trace, use the Translate Specific Element tab.
Translate a Type
- Select the renaming Map File.
- Enter the obfuscated Type Name.
- Click Translate.
- Review the translated stack trace in the Translation Report section.
Translate a Method
- Select the renaming Map File.
- Enter the obfuscated Type Name.
- Enter the obfuscated Method Name.
- (Optional) Select Method Signature and enter the method signature as it appears in the stack trace.
- Click Translate.
- Review the translated stack trace in the Translation Report section.
Providing the method signature can help distinguish between methods that share the same obfuscated name.
Ambiguous Results
When Overload Induction or Enhanced Overload Induction is enabled, multiple original methods may share the same obfuscated name.
In these cases, the Stack Trace Decoder displays every possible match. You can then use the method signature or surrounding stack trace information to determine the correct method.
Best Practices
- Always use the map file generated for the same version as the protected application.
- Provide method signatures when translating individual methods to improve accuracy.
- Store map files securely because they reveal the original names of obfuscated symbols.