mirror of
https://github.com/NationalSecurityAgency/ghidra.git
synced 2025-10-03 09:49:23 +02:00
GP-0: Some DevGuide fixes
This commit is contained in:
parent
75a87036e6
commit
47e207ab3e
1 changed files with 4 additions and 4 deletions
|
@ -247,7 +247,7 @@ see if we are already developing one. Of course, in time you might also search t
|
||||||
if others are developing one. There are quite a few caveats and gotchas, the most notable being that
|
if others are developing one. There are quite a few caveats and gotchas, the most notable being that
|
||||||
this interface is still in quite a bit of flux. When things go wrong, it could be because of,
|
this interface is still in quite a bit of flux. When things go wrong, it could be because of,
|
||||||
without limitation: 1) a bug on your part, 2) a bug on our part, 3) a design flaw in the interfaces,
|
without limitation: 1) a bug on your part, 2) a bug on our part, 3) a design flaw in the interfaces,
|
||||||
or 4) a bug in the debugger/API your adapting. We are still in the process of writing up this
|
or 4) a bug in the debugger/API you're adapting. We are still in the process of writing up this
|
||||||
documentation. In the meantime, we recommend using the GDB and dbgeng.dll agents as examples.
|
documentation. In the meantime, we recommend using the GDB and dbgeng.dll agents as examples.
|
||||||
|
|
||||||
You'll also need to provide launcher(s) so that Ghidra knows how to configure and start your
|
You'll also need to provide launcher(s) so that Ghidra knows how to configure and start your
|
||||||
|
@ -283,7 +283,7 @@ from there. Again, we have a bit of documentation to do regarding common pitfall
|
||||||
### Emulation
|
### Emulation
|
||||||
|
|
||||||
The most obvious integration path for 3rd-party emulators is to write a "connector." However, p-code
|
The most obvious integration path for 3rd-party emulators is to write a "connector." However, p-code
|
||||||
emulation is now an integral feature of the Ghidra UI, and it has a fairly accessible API. Namely
|
emulation is now an integral feature of the Ghidra UI, and it has a fairly accessible API. Namely,
|
||||||
for interpolation between machines states recorded in a trace, and extrapolation into future machine
|
for interpolation between machines states recorded in a trace, and extrapolation into future machine
|
||||||
states. Integration of such emulators may still be useful to you, but we recommend trying the p-code
|
states. Integration of such emulators may still be useful to you, but we recommend trying the p-code
|
||||||
emulator to see if it suits your needs for emulation in Ghidra before pursuing integration of
|
emulator to see if it suits your needs for emulation in Ghidra before pursuing integration of
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue