![]() ![]() Select to analyze strack trace for classes in the current project Paste here the external stack trace or thread dump. Put a stack trace or a complete thread dump here Specify the location of the unscrambler log file. You can develop your own plugin to unscramble stack trace of the code being processed with any other obfuscator. ![]() IntelliJ IDEA ships with the Zelix Klass Master unscrambler plugin. Here you can select the unscrambler tool. Select this checkbox to unscramble the external stack trace, if your source code is scrambled. The Try Blocks Highlighting feature in IntelliJ IDEA uses a bold dotted underline for such statements in the stack trace. These calls occur inside the try/catch/finally block and can potentially throw an exception. Some calls in the Run tool window have a dotted underline. In case of thread dump, IntelliJ IDEA will present all threads in a readable way and sort them to show first those most probably responsible for the deadlock or hang-problem. To jump to the code that caused the problem, scroll to the stack trace line you need and click the link to the source file. The stack trace is displayed in the Run tool window. If you want to explicitly specify the directory with the corresponding dSYM files, select the Use additional directory to search for missing dSYMs checkbox and enter the desired directory in the field or choose it from the file system.Ĭlick OK. If the stack trace text is corrupted (lines are cut or wrapped, or too long, and so on) after processing with some software (for example, a bug tracker or a mail client), click Normalize. To do that, select the Unscramble stack trace checkbox, select the desired unscrambler and log file. ![]() Specify whether you want to have the stack trace unscrambled. In the Analyze Stack Trace dialog that opens, paste the external stack trace or thread dump into the Put a stack trace or a complete thread dump here: text area. With IntelliJ IDEA, you can copy an exception or full thread dump, paste it to the Stack Trace Analyzer, explore information, and navigate to the corresponding source code.įrom the main menu, select Code | Analyze Stack Trace or Thread Dump. Moreover, the source code can be scrambled. Unlike the exceptions that you get in the debug mode or when running unit tests, these exceptions do not have links that help you navigate to the corresponding locations in the source code. You might want to analyze exceptions received by someone else, for example, QA engineers, or investigate a deadlock, or a hang-problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |