mirror/ghidra
1
0
Fork 0
mirror of https://github.com/NationalSecurityAgency/ghidra.git synced 2026-09-28 17:11:11 -09:00
Code Issues Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/GP-3218_Dan_deleteToolColorsSections--SQUASHED'

Browse Source
This commit is contained in:
Ryan Kurtz
2023-04-24 06:46:35 -04:00
parent 98f0a1cc57 e925574dc0
commit b2c59bf6de
6 changed files with 27 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerBreakpointMarkerPlugin/DebuggerBreakpointMarkerPlugin.html
View File

@@ -32,6 +32,9 @@
the current target. <B>NOTE:</B> Depending on the connected debugger, locations resulting from
a common specification may not be independently manipulated.</P>
<P>By default, enabled breakpoints are colored a desaturated blue, ineffective breakpoints are
colored grey, and disabled breakpoints have no background at all.</P>
<H2>In the Decompiler</H2>
<TABLE width="100%">
@@ -132,12 +135,5 @@
<P>This action is available when there is at least one breakpoint (in any state) at the cursor.
It deletes those logical breakpoints.</P>
<H2><A name="colors"></A>Tool Options: Colors</H2>
<P>The background coloring of enabled and disabled, effective and ineffective breakpoints can
be configured in the tool's options. By default, enabled breakpoints are colored a desaturated
blue, ineffective breakpoints are colored grey, and disabled breakpoints have no background at
all.</P>
</BODY>
</HTML>

4
Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerListingPlugin/DebuggerListingPlugin.html
View File

@@ -246,9 +246,5 @@
<LI>Read Visible Memory, RO Once - (default) behaves like Read Visible Memory, except it will
neglect read-only ranges that have been read previously.</LI>
</UL>
<H2><A name="colors"></A>Tool Options: Colors</H2>
<P>The memory-state and tracked-location background colors can all be configured here.</P>
</BODY>
</HTML>

5
Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerMemoryBytesPlugin/DebuggerMemoryBytesPlugin.html
View File

@@ -129,10 +129,5 @@
trace's editing mode is set to Read-Only in the tool. <B>NOTE:</B> This toggle also disables
automatic navigation in order to prevent the cursor from being moved unexpectedly while typing
edits.</P>
<H2><A name="colors"></A>Tool Options: Colors</H2>
<P>The memory-state and tracked-location background colors are replicated from the <A href=
"help/topics/DebuggerListingPlugin/DebuggerListingPlugin.html">Dynamic Listing</A>.</P>
</BODY>
</HTML>

27
Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerRegistersPlugin/DebuggerRegistersPlugin.html
View File

@@ -28,6 +28,18 @@
for the target processor. It permits for the selection, organization, display, search,
modification, and analysis of the registers and values.</P>
<P>The register window uses colors to hint about the state of registers and their values. By
default, changed registers are displayed in red, and stale registers are displayed in dark
grey. A "stale" register is one whose current value is not known. The value displayed is the
last recorded value or the default value 0. Simply, a "changed" register is one whose value has
just changed. For example, if a register is modified as result of stepping, then that register
is changed. However, given the possibility of rewinding, changing thread focus, etc., "changed"
is actually subtly more flexible. The registers window remembers the user's last coordinates
(time, thread, frame, etc.) as well as the current coordinates. So, "changed" more precisely
refers to a register whose value differs between those two coordinates. This permits the user
to switch focus between different coordinates and quickly identify what is different, so long
as those coordinates pertain to the same processor language.</P>
<H2>Table Columns</H2>
<P>The table displays information about registers, including their values and types. It has the
@@ -109,20 +121,5 @@
<P>This button is analogous to the "snapshot" action of other Ghidra windows. It generates a
clone of this window. The clone will no longer follow the current thread, but it will follow
the current time.</P>
<H2><A name="colors"></A>Tool Options: Colors</H2>
<P>The register window uses colors to hint about the state of registers and their values. They
can be configured in the tool's options. By default, changed registers are displayed in red,
and stale registers are displayed in dark grey. A "stale" register is one whose current value
is not known. The value displayed is the last recorded value or the default value 0. Simply, a
"changed" register is one whose value has just changed. For example, if a register is modified
as result of stepping, then that register is changed. However, given the possibility of
rewinding, changing thread focus, etc., "changed" is actually subtly more flexible. The
registers window remembers the user's last coordinates (time, thread, frame, etc.) as well as
the current coordinates. So, "changed" more precisely refers to a register whose value differs
between those two coordinates. This permits the user to switch focus between different
coordinates and quickly identify what is different, so long as those coordinates pertain to the
same processor language.</P>
</BODY>
</HTML>

5
Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerTraceViewDiffPlugin/DebuggerTraceViewDiffPlugin.html
View File

@@ -149,10 +149,5 @@
<P>These actions are only present when the comparison listing is visible. Each is available
when there exists a previous or next range from the main listing's cursor. Clicking the action
navigates to the nearest address in that range.</P>
<H2><A name="colors"></A>Tool Options: Colors</H2>
<P>The difference highlight color is replicated from the <A href=
"help/topics/Diff/Diff.htm">Program Differences</A> plugin.</P>
</BODY>
</HTML>

27
Ghidra/Debug/Debugger/src/main/help/help/topics/DebuggerWatchesPlugin/DebuggerWatchesPlugin.html
View File

@@ -30,6 +30,18 @@
applicable, that data type can optionally be applied to the trace database. Some metadata about
the watch is also given, e.g., the address of the value.</P>
<P>The watch window uses colors to hint about changes in and freshness of displayed values. By
default, changed values are displayed in red, and stale values are displayed in dark grey. A
"stale" value is one which depends on any register or memory whose contents are not known. The
value displayed is that computed from the last recorded contents, defaulting to 0 when never
recorded. Simply, a "changed" watch is one whose value has just changed. For example, if a
value changes as result of stepping, then that watch is changed. However, given the possibility
of rewinding, changing thread focus, etc., "changed" is actually subtly more flexible. The
watch remembers the evaluation from the user's last coordinates (time, thread, frame, etc.) as
well as the current coordinates. So, "changed" more precisely refers to a watch whose value
differs between those two coordinates. This permits the user to switch focus between different
coordinates and quickly identify what is different.</P>
<H2>Examples</H2>
<P>For those less familiar with Sleigh, here are some example expressions:</P>
@@ -162,20 +174,5 @@
"help/topics/DebuggerControlPlugin/DebuggerControlPlugin.html">Control and Machine State
Plugin</A>. <B>Note:</B> Only the raw "Value" column can be edited directly. The "Repr" column
cannot be edited, yet.</P>
<H2><A name="colors"></A>Tool Options: Colors</H2>
<P>The watch window uses colors to hint about changes in and freshness of displayed values.
They can be configured in the tool's options. By default, changed values are displayed in red,
and stale values are displayed in dark grey. A "stale" value is one which depends on any
register or memory whose contents are not known. The value displayed is that computed from the
last recorded contents, defaulting to 0 when never recorded. Simply, a "changed" watch is one
whose value has just changed. For example, if a value changes as result of stepping, then that
watch is changed. However, given the possibility of rewinding, changing thread focus, etc.,
"changed" is actually subtly more flexible. The watch remembers the evaluation from the user's
last coordinates (time, thread, frame, etc.) as well as the current coordinates. So, "changed"
more precisely refers to a watch whose value differs between those two coordinates. This
permits the user to switch focus between different coordinates and quickly identify what is
different.</P>
</BODY>
</HTML>