Analyze Stacktrace Dialog
Tools | Analyze Stacktrace
Use this dialog box to reach a navigable console stack trace for external applications.
From each message in this stack trace, you can navigate right to the source code that cased the reported problem.
||Select this check box to unscramble the external stack trace, if your source code is scrambled.
||Here you can select the unscrambler tool.
ships with the Zelix Klass Master unscrambler
plugin. You can develop your own plugin
to unscramble stack trace of the code being processed with any other obfuscator.
||Specify the location of the unscrambler log file.
|Put a stack trace or a complete thread dump here
||Paste here the external stack trace or thread dump.
Automatically detect and analyze thread dumps copied to
the clipboard outside of PhpStorm.
||If this check box is selected, PhpStorm will monitor and analyze the contents of the clipboard. You
can select this check box only once and your clipboard will be scanned every time you switch to PhpStorm.
As soon as something looking like a stack trace gets copied to the clipboard,
PhpStorm will show this stack trace in the corresponding tool window.
Show changed in last <this_many> days
||Select this check box to specify the time period in which you want to check last changes in stack traces. The default time
period is set to 31 days.
||If the stack trace text is corrupted (lines are cut or wrapped, or too long, etc.)
after processing with some software (for example, bug tracker or mail client),
click this button to restore the normal stack trace structure.
Last modified: 29 January 2015