diff --git a/Ghidra/Debug/Debugger/certification.manifest b/Ghidra/Debug/Debugger/certification.manifest
index 1e12776852..9f50cd3e65 100644
--- a/Ghidra/Debug/Debugger/certification.manifest
+++ b/Ghidra/Debug/Debugger/certification.manifest
@@ -38,11 +38,12 @@ src/main/help/help/topics/DebuggerBreakpointsPlugin/images/breakpoint-mixed-ed.p
src/main/help/help/topics/DebuggerBreakpointsPlugin/images/breakpoints-clear-all.png||GHIDRA||||END|
src/main/help/help/topics/DebuggerBreakpointsPlugin/images/breakpoints-disable-all.png||GHIDRA||||END|
src/main/help/help/topics/DebuggerBreakpointsPlugin/images/breakpoints-enable-all.png||GHIDRA||||END|
+src/main/help/help/topics/DebuggerConsolePlugin/DebuggerConsolePlugin.html||GHIDRA||||END|
+src/main/help/help/topics/DebuggerConsolePlugin/images/DebuggerConsolePlugin.png||GHIDRA||||END|
src/main/help/help/topics/DebuggerInterpreterPlugin/DebuggerInterpreterPlugin.html||GHIDRA||||END|
src/main/help/help/topics/DebuggerListingPlugin/DebuggerListingPlugin.html||GHIDRA||||END|
src/main/help/help/topics/DebuggerListingPlugin/images/DebuggerGoToDialog.png||GHIDRA||||END|
src/main/help/help/topics/DebuggerListingPlugin/images/DebuggerListingPlugin.png||GHIDRA||||END|
-src/main/help/help/topics/DebuggerListingPlugin/images/DebuggerModuleImportDialog.png||GHIDRA||||END|
src/main/help/help/topics/DebuggerMemviewPlugin/DebuggerMemviewPlugin.html||GHIDRA||||END|
src/main/help/help/topics/DebuggerMemviewPlugin/images/DebuggerMemviewPlugin.png||GHIDRA||||END|
src/main/help/help/topics/DebuggerMemviewPlugin/images/DebuggerMemviewPlugin_old.png||GHIDRA||||END|
diff --git a/Ghidra/Debug/Debugger/src/main/help/help/TOC_Source.xml b/Ghidra/Debug/Debugger/src/main/help/help/TOC_Source.xml
index a9902c2ef8..d21c44c30c 100644
--- a/Ghidra/Debug/Debugger/src/main/help/help/TOC_Source.xml
+++ b/Ghidra/Debug/Debugger/src/main/help/help/TOC_Source.xml
@@ -74,6 +74,10 @@
target="help/topics/DebuggerModelServicePlugin/DebuggerModelServicePlugin.html" />
+
The first place to look when you're having trouble is the error console. In Eclipse, this is - just the "Console" window. In Ghidra, it can be accessed from the main application window. - Sometimes it reports known issues; sometimes it reports unexpected behavior; etc., which may be +
The first place to look when you're having trouble is the Debug Console. Second, if you're + in 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 class. These typically offer clues to exactly what has gone wrong.
In the Dynamic Listing:
The console logs messages from Ghidra related to the debugger. Depending on the exact + configuration, this can comprise a wide range of components, including all GUI views, active + connectors, and running agents. Currently, it implements an appender to gather all Log4J + messages emitted by Ghidra and filters for debugger-related packages and a level in the range + INFO through and including FATAL. That feature will likely be removed as more components are + programmed to work directly with the console. Soon, it may also provide a command-line + interface to control Ghidra's debugging sessions and interact with traces.
+ +Some log messages include an action context, allowing plug-ins to offer actions on that + message. These are said to be "actionable" messages. A noteworthy example is when navigating to + a module that could not be automatically mapped from the current project. Instead of displaying + a prompt, it will log a message and suggest actions to resolve the issue. A successful + resolution typically removes the message from the log. Note that additional actions may be + available from the context menu.
+ +By default, the log is sorted so that actionable messages appear at the top. Then, it is + sorted by descending date, so that the most recent messages appear at the top. Like any other + Ghidra table, it can customized and filtered. Note that the filter box is at the top, because + we anticipate a command-line input in the future, which we'd like to place at the bottom.
+ +The table has the following columns:
+ +Not considering extension actions from other plugins, the console provides the + following:
+ +Removes all messages, including actionable messages, from the log.
+ + diff --git a/Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerConsolePlugin/images/DebuggerConsolePlugin.png b/Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerConsolePlugin/images/DebuggerConsolePlugin.png new file mode 100644 index 0000000000..79f8089b97 Binary files /dev/null and b/Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerConsolePlugin/images/DebuggerConsolePlugin.png differ diff --git a/Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerInterpreterPlugin/DebuggerInterpreterPlugin.html b/Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerInterpreterPlugin/DebuggerInterpreterPlugin.html index e697480995..16706c488c 100644 --- a/Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerInterpreterPlugin/DebuggerInterpreterPlugin.html +++ b/Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerInterpreterPlugin/DebuggerInterpreterPlugin.html @@ -42,9 +42,9 @@ immediately upon the associated target interpreter becoming invalid, i.e., the connection was closed. Pinning an interpreter keeps it open, but in a disabled state, so that the buffer can be examined after invalidation. - +This action is always available. It interrupts the current target's execution.