mirror of
https://github.com/NationalSecurityAgency/ghidra
synced 2024-10-30 02:29:46 +00:00
GP-0 Additional edits for 10.3 docs
This commit is contained in:
parent
2d63324b3b
commit
989922f599
1 changed files with 9 additions and 9 deletions
|
@ -110,7 +110,7 @@
|
|||
which ruled out displaying accurate stack frames during emulation. There is still more work for full UI integration, but you can
|
||||
unwind a stack (whether on target or emulated) using the <b>Debugger -> Analysis</b> menu and view the results by navigating the
|
||||
<b>Dynamic Listing</b> to stack space. Please understand it may not work in most situations, yet.</li>
|
||||
<li>We have added several miscellaneous actions: To invalidate the Emulator cache, use the Debugger -> Configure Emulator menu.
|
||||
<li>Several miscellaneous actions have been added: To invalidate the Emulator cache, use the Debugger -> Configure Emulator menu.
|
||||
Use this whenever the Emulator seems to be ignoring configuration changes, especially when modifying custom Sleigh breakpoints.
|
||||
To display all bytes (not just changed ones) in the Dynamic Listing, choose Load Bytes from Emulator in the Auto-Read drop-down.
|
||||
To manually add or remove memory regions, e.g., to create and initialize a heap for emulation, use the new actions in the Regions window</li>
|
||||
|
@ -124,16 +124,16 @@
|
|||
live target or the Emulator. The Emulator stepping actions have been removed from the <b>Threads</b> panel. (They never really made sense there.)
|
||||
Toggling these actions to the Emulator effectively forks an emulator from the target's live state, i.e., for extrapolation, just as the old
|
||||
emulator stepping actions did.</li>
|
||||
<li>We added text in the top right of the <b>Dynamic Listing</b> to display the current program counter (or whatever the listing is configured to
|
||||
<li>The current program counter is now displayed in the top right corner of the <b>Dynamic Listing</b> (or whatever the listing is configured to
|
||||
track). It will display in red if the address cannot be shown in the listing, e.g., because it is not mapped in memory. This provides better
|
||||
feedback when the listings seem to be out of sync.</li>
|
||||
<li>We added GDB's advance command to the Listing context menus as well as the equivalent actions for other debuggers. (More generally,
|
||||
<li>GDB's advance command has been added to the Listing context menus as well as the equivalent actions for other debuggers. (More generally,
|
||||
any command provided by a back-end connector that takes a single address parameter is presented in context menus where an address is
|
||||
available.)</li>
|
||||
<li>The <b>Go To dialog</b> in the <b>Dynamic Listing</b> can now take simple addresses in hexadecimal. Previously, it only took Sleigh expressions,
|
||||
which are powerful, but made the common case too complicated. It still accepts Sleigh expressions, and those expressions can now refer
|
||||
to labels (symbols) from any mapped program database (static image). </li>
|
||||
<li>We added a new kind of hover on variables. If there is a debugger target (live or emulated) mapped to the current program,
|
||||
<li>A new kind of hover has been added for displayed variables. If there is a debugger target (live or emulated) mapped to the current program,
|
||||
the hover will display the variable’s current value. This applies to Listings and the Decompiler window. </li>
|
||||
<li>You can now select a different thread, frame, or snapshot without activating it. Single-click to select. Double-click to activate.</li>
|
||||
</ul>
|
||||
|
@ -143,7 +143,7 @@
|
|||
<ul>
|
||||
<li>You can now set the working directory when launching a Windows target. </li>
|
||||
<li>GADP agents now accept a single connection and automatically terminate when Ghidra disconnects. </li>
|
||||
<li>We added launch scripts for starting a GADP agent from the command line. </li>
|
||||
<li>Launch scripts have been added for starting a GADP agent from the command line. </li>
|
||||
<li>There is now a script to build the Java bindings needed for the LLDB connector. </li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
|
@ -174,7 +174,7 @@
|
|||
on the declared size of an int from the data organization used to parse. A future version will have a setting to size all parsed enums
|
||||
to the smallest size that will fit all the values. </P>
|
||||
|
||||
<H3>C Header File Parsing </H3>
|
||||
<H2>C Header File Parsing </H2>
|
||||
<P>The C-Parser GUI has been refactored to remove include paths from the Options section done as –D define lines, to a new Include section.
|
||||
This should make it easier to configure paths to the include files and has the added benefit of coloring the include file entries red if
|
||||
they are not found within any include path. You may find creating and using a Ghidra Script instead of the GUI an easier repeatable process.
|
||||
|
@ -218,11 +218,11 @@
|
|||
|
||||
<P>Two new user-submitted processors, eBPF and BPF, add support for two variants of Berkeley Packet Filter binaries.</P>
|
||||
|
||||
<P>A user-submitted refactoring of X86 LOCK/UNLOCK decoding and semantics has been committed. There are currently some issues with the
|
||||
Decompiler re-arranging code outside of the LOCK/UNLOCK which will be addressed an upcoming patch. If your analysis depends on
|
||||
<P>A user-submitted refactoring of X86 <code>LOCK/UNLOCK</code> decoding and semantics has been committed. There are currently some issues with the
|
||||
Decompiler re-arranging code outside of the <code>LOCK/UNLOCK</code> which will be addressed an upcoming patch. If your analysis depends on
|
||||
the LOCK/UNLOCK semantics, please be aware of the issue. </P>
|
||||
|
||||
<P> A new “leading zeroes count” operator, called lzcount, has been added to p-code, and it can now be used by SLEIGH developers
|
||||
<P> A new “leading zeroes count” operator, called <code>lzcount</code>, has been added to p-code, and it can now be used by SLEIGH developers
|
||||
to model processor instructions. The Decompiler can simplify common code idioms using these instructions, and emulation is supported.</P>
|
||||
|
||||
<H2>User Interface Improvements</H2>
|
||||
|
|
Loading…
Reference in a new issue