Debugger: Troubleshooting

Often, it's a good idea to troubleshoot by using the target platform's recommended debugger without connecting it to Ghidra. If it doesn't work there, it's not likely to work in Ghidra, since it relies on that debugger. For Linux, use gdb; for Windows, use WinDbg; for macOS, use LLDB.

Error Console

The first place to look when you're having trouble is the Debug Console. Second, if you're running from Eclipse, you can check its "Console" window. Often, Ghidra's Debug Console will offer actions to help you resolve a well-known issue or configuration problem. It also duplicates the error log when those messages are emitted from a debugger-related component. These typically offer clues to exactly what has gone wrong.

Settings and Toggles

This list is not exhaustive, but here are some options to examine if you're having trouble. In the FrontEnd tool, under Edit → Tool Options, select "Debugger.Workflow."

In the Dynamic Listing:

In the Objects provider:

In the Threads provider:

In the Debugger menu:

Additional troubleshooting recommendations are given in the Debugger course materials.