mirror of
https://github.com/NationalSecurityAgency/ghidra.git
synced 2026-01-09 22:17:55 -05:00
Many typo's
These were found using the command below searching for duplicated words, and manually going through the results to remove the false positives and reword the true positives. Sometimes I removed the doubled word and sometimes I replaced the duplicated word. The grep command: grep -nIEr '\b([a-zA-Z]+)[[:space:]*]+\1\b' ./Ghidra
This commit is contained in:
@@ -12,7 +12,7 @@ To perform an Overview Query, select **BSim -> Perform Overview...** from the Co
|
||||
You should see the following result:
|
||||

|
||||
1. Sort the table by the "Hit Count" column in ascending order. Typically, the functions with the largest hit counts will have low self-significance.
|
||||
Verify that that is the case for this table.
|
||||
Verify that that is the case for this table.
|
||||
1. Q: Examine the functions with the highest hit count. Why are there so many matches for these functions?
|
||||
<details><summary>Answer:</summary> These are all instances of PostgreSQL statistics-reporting functions. Their bodies are quite similar and they have identical BSim signatures.</details>
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ Finally, we briefly mention a few other topics related to BSim.
|
||||
|
||||
## Scripting BSim
|
||||
|
||||
There are are number of example scripts in the ``BSim`` script category, which demonstrate how to interact with BSim programmatically.
|
||||
There are a number of example scripts in the ``BSim`` script category, which demonstrate how to interact with BSim programmatically.
|
||||
|
||||

|
||||
|
||||
|
||||
@@ -1534,12 +1534,11 @@ Before you can do anything else, you must first create a project. Projects are u
|
||||
<p>
|
||||
<b><u>Notes:</u></b>
|
||||
<ul>
|
||||
|
||||
<li>The <b>Convert</b> action only appears on the right mouse menu if the cursor is on a constant operand. It only works on the current scalar.</li>
|
||||
<li>The <b>Set Equate...</b> action only appears on right mouse menu if the cursor is on a constant operand. It works on the current scalar and if there is a selection on all matching scalars in the selection.</li>
|
||||
<li>To group Equates or Enums into a single Enum in the Data Type Manager, use the filter to group them (if possible), select them using click and drag, then do <b>right-click->Create Enum from Selection</b>.</li>
|
||||
<li>The <b>Apply Enum...</b> action allows users to apply the enum names to multiple matching values in an instruction or selection of instructions. It only appears on the right mouse menu if the cursor is on a constant operand (no selection) or there are are constant operands in the current selection.</li>
|
||||
<li>Applying Equates and Enums to the Listing will rename most in the decompiler, however...</li>
|
||||
<li>The <b>Apply Enum...</b> action allows users to apply the enum names to multiple matching values in an instruction or selection of instructions. It only appears on the right mouse menu if the cursor is on a constant operand (no selection) or there are constant operands in the current selection.</li>
|
||||
<li>Applying Equates and Enums to the Listing will rename most in the decompiler, however...</li>
|
||||
<li><b>PREFERRED METHOD:</b> To apply Enum names to the decompiler view, find a variable being assigned or compared to the constants then do <b>right-click->Retype variable</b> or <b>right-click->Retype global</b>. Make sure that the Enum size (1,2,4,or 8 bytes) matches the size of the variable in the decompiler or it will not display the names.</li>
|
||||
</ul>
|
||||
</p>
|
||||
@@ -1735,7 +1734,7 @@ Before you can do anything else, you must first create a project. Projects are u
|
||||
<li>In the Program Tree, right-click on a <b>CODE</b> segment and choose <b>Modularize By->:</b>
|
||||
<ul>
|
||||
<li><b>Subroutine-></b> This breaks code into segments by a chosen subroutine model.</li>
|
||||
<li><b>Complexity Depth</b> This groups functions into folders Level 0 to n, where Level 0 contains the entry function(s), Level 1 contains functions called by entry functin(s), and so on. Level n contains functions that do not call any other functions within the current program but may call external functions.</li>
|
||||
<li><b>Complexity Depth</b> This groups functions into folders Level 0 to n, where Level 0 contains the entry function(s), Level 1 contains functions called by entry function(s), and so on. Level n contains functions that do not call any other functions within the current program but may call external functions.</li>
|
||||
<li><b>Dominance</b> This groups functions in folders according to which functions dominate other functions. Function A dominates Function B if every path from the entry to Function B must go through Function A.</li>
|
||||
</ul>
|
||||
</ul>
|
||||
|
||||
@@ -162,7 +162,7 @@ src="images/breakpoint-enable.png" alt="set breakpoint" /> Set
|
||||
Breakpoint, press <strong><code>K</code></strong> on the keyboard, or
|
||||
double-click the margin.</li>
|
||||
<li>From the Breakpoints window, use the <strong>Set Breakpoint</strong>
|
||||
dropdown to to access the various breakpoint actions defined by
|
||||
dropdown to access the various breakpoint actions defined by
|
||||
GDB.</li>
|
||||
<li>From the Terminal window, use the GDB command, e.g.,
|
||||
<code>break main</code>.</li>
|
||||
|
||||
@@ -17,7 +17,7 @@ From here, you can toggle and delete existing breakpoints.
|
||||
There are several ways to set a new breakpoint:
|
||||
|
||||
1. From any static or dynamic listing window, including Disassembly, Memory/Hex, and the Decompiler, right-click and select  Set Breakpoint, press **`K`** on the keyboard, or double-click the margin.
|
||||
1. From the Breakpoints window, use the **Set Breakpoint** dropdown to to access the various breakpoint actions defined by GDB.
|
||||
1. From the Breakpoints window, use the **Set Breakpoint** dropdown to access the various breakpoint actions defined by GDB.
|
||||
1. From the Terminal window, use the GDB command, e.g., `break main`.
|
||||
|
||||
The advantage of using the listings is that you can quickly set a breakpoint at any address.
|
||||
|
||||
@@ -124,7 +124,7 @@ using any unzip program (built-in OS utilities, 7-Zip, WinZip, WinRAR, etc).
|
||||
3. Click `Environment variables...`
|
||||
3. Add the JDK bin directory to the PATH variable:
|
||||
1. Under `System variables`, highlight `Path` and click `Edit...`
|
||||
2. At the end of the the `Variable value` field, add a semicolon followed by
|
||||
2. At the end of the `Variable value` field, add a semicolon followed by
|
||||
`<path of extracted JDK dir>\bin`, or use the `New` button in the
|
||||
`Edit environment variable` window to add a new entry to the `Path`.
|
||||
3. Click `OK`
|
||||
@@ -268,7 +268,7 @@ A single `ghidra.jar` file can be created using the `<GhidraInstallDir>/support/
|
||||
script.
|
||||
|
||||
### PyGhidra Mode
|
||||
Ghidra has integrated the the popular Pyhidra extension to enable native CPython 3 support out of
|
||||
Ghidra has integrated the popular Pyhidra extension to enable native CPython 3 support out of
|
||||
the box. To enable this support, Ghidra must be launched from a Python environment using special
|
||||
launch scripts.
|
||||
1. Navigate to `<GhidraInstallDir>/support/`
|
||||
|
||||
Reference in New Issue
Block a user