Nixyri/ghidra
1
0
Fork 0
mirror of https://github.com/NationalSecurityAgency/ghidra.git synced 2025-02-16 07:30:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Frequently asked questions (markdown)

Dan 2019-03-07 10:12:44 -05:00
parent a207f55a68
commit 2845261b88
1 changed files with 20 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
Frequently-asked-questions.md

@ -14,7 +14,10 @@ Ghidra uses an existing Java runtime on the PATH (Java 1.7 or later) to locate a
This repository is a placeholder for the full open source release.
Be assured **efforts are under way** to make the software available here.
In the meantime, enjoy using Ghidra on your SRE efforts, developing your
We plan to include our build scripts (for Gradle) and a developer's guide.
We plan also to include the source for the native components, which includes the code for the decompiler.
In the meantime, enjoy using Ghidra on your SRE efforts.
Also try out the GhidraDev plugin for Eclipse to develop your
own scripts and plugins, and perusing the over a million lines of Java and
Sleigh code released within the initial public release.
The release can be downloaded from our project homepage at www.ghidra-sre.org.
@ -28,3 +31,19 @@ Ghidra provides the ability to invert the colors of its GUI, providing a "darkis
### How do I change Ghidra's key bindings?
You can change the key binding of any top level menu or context sensitive menu item (except items in the Code Browser's "Window" menu). Simply hover on the menu item and hit the F4 key to change the key binding. Alternatively, you change the key bindings of your current tool via Edit → Tool Options... → Key Bindings.
### There are missing instructions or bad instructions. What can I do?
You have a couple of options:
First, you can submit an issue, but we make no promises to address any particular issue.
Second, you can modify the Sleigh specification yourself.
If you anticipate substantial changes, e.g., supporting a new variant, we recommend you make a copy of the ```.slaspec``` file, name it appropriately, and update the ```.lspec``` file to include it.
Optionally, you may submit a patch or pull request with your modifications if you'd like to contribute them to the broader community.
Please see our contribution guidelines for more information.
The Sleigh source consists of the ```.sinc``` and ```.slaspec``` files in the ```data/languages``` directory of each processor module.
When these are updated, Ghidra should automatically compile them, producing ```.sla``` files, the next time the processor is used.
You may need to restart Ghidra to convince it to recompile.
The documentation for our Sleigh language is at ```docs/languages/index.html```.
There is also a useful script for debugging: ```DebugSleighInstructionParse.java```.
Put you cursor at the start of the faulty/missing instruction and run it for a rather verbose dump as it attempts to parse the instruction.