yetangitu/ghidra
1
0
Fork 0
mirror of https://github.com/NationalSecurityAgency/ghidra.git synced 2025-10-03 09:49:23 +02:00
Code Issues Releases Wiki Activity

GP-0 more bsim tutorial typos

Browse source
This commit is contained in:
James 2023-12-18 22:00:40 +00:00
parent 2fa140f6f8
commit 7c88892b18
4 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
GhidraDocs/GhidraClass/BSim/BSimTutorial_Basic_Queries.html
View file

@ -135,7 +135,7 @@ We use these different versions to demonstrate some of the capabilities of BSim.
<ul> <ul>
<li>The <strong>Listing View</strong> tab shows the disassembly.</li> <li>The <strong>Listing View</strong> tab shows the disassembly.</li>
<li>The <strong>Decompiler Diff View</strong> tab shows the decompiled code.</li> <li>The <strong>Decompiler Diff View</strong> tab shows the decompiled code.</li>
<li>Differences in the code are automatically highlighted in blue.</li> <li>Differences in the code are automatically highlighted in cyan.</li>
<li>Either view can be toggled between a horizontal split and a vertical split using the drop-down menu.</li> <li>Either view can be toggled between a horizontal split and a vertical split using the drop-down menu.</li>
</ul> </ul>
</li> </li>

2
GhidraDocs/GhidraClass/BSim/BSimTutorial_Basic_Queries.md
View file

@ -111,7 +111,7 @@ We use these different versions to demonstrate some of the capabilities of BSim.
1. Right-click on the row of the match and perform the **Compare Functions** action to bring up the side-by-side comparison. 1. Right-click on the row of the match and perform the **Compare Functions** action to bring up the side-by-side comparison.
- The **Listing View** tab shows the disassembly. - The **Listing View** tab shows the disassembly.
- The **Decompiler Diff View** tab shows the decompiled code. - The **Decompiler Diff View** tab shows the decompiled code.
- Differences in the code are automatically highlighted in blue. - Differences in the code are automatically highlighted in cyan.
- Either view can be toggled between a horizontal split and a vertical split using the drop-down menu. - Either view can be toggled between a horizontal split and a vertical split using the drop-down menu.
1. Examine the diff views to verify that the match is valid. 1. Examine the diff views to verify that the match is valid.
1. Using the **Apply Name** action in the BSim Search Results table, apply the name from the search result to the queried function. 1. Using the **Apply Name** action in the BSim Search Results table, apply the name from the search result to the queried function.

4
GhidraDocs/GhidraClass/BSim/BSimTutorial_Evaluating_Matches.html
View file

@ -26,7 +26,7 @@ While doing this, we’ll showcase some of the features available in the decompi
The corresponding function in <code>postgres</code> should have a default name.</li> The corresponding function in <code>postgres</code> should have a default name.</li>
<li>Examine this match in the side-by-side decompiler view. <li>Examine this match in the side-by-side decompiler view.
Note that the matching function has better data type information due to the debug information.</li> Note that the matching function has better data type information due to the debug information.</li>
<li>Q: Why does the placement of the <code>double</code> argument between the functions? <li>Q: Why does the placement of the <code>double</code> argument differ between the functions?
<details><summary>Answer</summary> Floating point values and integer/pointer values are passed in separate sets of registers. <details><summary>Answer</summary> Floating point values and integer/pointer values are passed in separate sets of registers.
Neither ordering is wrong since both are consistent with the instructions of the function. Neither ordering is wrong since both are consistent with the instructions of the function.
The debug info records a specific signature (and ordering) for the function, which Ghidra applies. The debug info records a specific signature (and ordering) for the function, which Ghidra applies.
@ -44,7 +44,7 @@ Some terminology: if you click on a token in a decompiler panel, that token beco
<p>The colors:</p> <p>The colors:</p>
<ul> <ul>
<li>Blue is used to highlight differences between the two functions.</li> <li>Cyan is used to highlight differences between the two functions.</li>
<li>Pink is used to highlight the focused token and its match.</li> <li>Pink is used to highlight the focused token and its match.</li>
<li>Lavender is used to highlight the focused token when it does not have a match.</li> <li>Lavender is used to highlight the focused token when it does not have a match.</li>
<li>Orange is used to highlight the focused token when it is ineligible for match. <li>Orange is used to highlight the focused token when it is ineligible for match.

4
GhidraDocs/GhidraClass/BSim/BSimTutorial_Evaluating_Matches.md
View file

@ -22,7 +22,7 @@ Import and analyze the stripped `postgres` executable into the tutorial project,
The corresponding function in `postgres` should have a default name. The corresponding function in `postgres` should have a default name.
1. Examine this match in the side-by-side decompiler view. 1. Examine this match in the side-by-side decompiler view.
Note that the matching function has better data type information due to the debug information. Note that the matching function has better data type information due to the debug information.
1. Q: Why does the placement of the `double` argument between the functions? 1. Q: Why does the placement of the `double` argument differ between the functions?
<details><summary>Answer</summary> Floating point values and integer/pointer values are passed in separate sets of registers. <details><summary>Answer</summary> Floating point values and integer/pointer values are passed in separate sets of registers.
Neither ordering is wrong since both are consistent with the instructions of the function. Neither ordering is wrong since both are consistent with the instructions of the function.
The debug info records a specific signature (and ordering) for the function, which Ghidra applies. The debug info records a specific signature (and ordering) for the function, which Ghidra applies.
@ -37,7 +37,7 @@ Some terminology: if you click on a token in a decompiler panel, that token beco
The colors: The colors:
- Blue is used to highlight differences between the two functions. - Cyan is used to highlight differences between the two functions.
- Pink is used to highlight the focused token and its match. - Pink is used to highlight the focused token and its match.
- Lavender is used to highlight the focused token when it does not have a match. - Lavender is used to highlight the focused token when it does not have a match.
- Orange is used to highlight the focused token when it is ineligible for match. - Orange is used to highlight the focused token when it is ineligible for match.