IntelliJ IDEA 2020.1 Help

Analyze external stack traces

You might want to analyze exceptions received by someone else, for example, QA engineers, or investigate a deadlock, or a hang-problem. 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. Moreover, the source code can be scrambled.

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.

  1. From the main menu, select Analyze | Stack Trace or Thread Dump.

  2. 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.

  3. Specify whether you want to have the stack trace unscrambled. To do that, select the Unscramble stack trace checkbox, select the desired unscrambler and log file.

  4. 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.

  5. 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.

  6. Click OK. The stack trace is displayed in the Run tool window.

    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 file opens in the editor.

    A thred dump shown in the Run tool window

Some calls in the Run tool window have a dotted underline. These calls occur inside the try/catch/finally block and can potentially throw an exception. The Try Blocks Highlighting feature in IntelliJ IDEA uses a bold dotted underline for such statements in the stack trace.

the Try Blocks Highlighting feature highlights calls in the Run tool window
Last modified: 2 June 2020