I know that there are people who cannot tell the difference between IDA and other tools. It is perfectly understandable that they would prefer free solutions (if the result is the same, why pay?) Our tools are used by the elite, as someone put it.
Example of how the declarativeness of Ghidra makes things easy: I ran into an issue with a Win32 stack check function being assumed to clobber the FP stack, breaking dataflow analysis for functions that return floats. Fixed by editing an XML file to add a new calling convention.
-
-
(I also filed a bug, because it would be much more convenient if that were a configurable override in the per-function calling convention UI, which requires actual code changes to implement, but the point is I *could* fix it without touching the code and keep reversing.)
-
On that note, I find Ghidra's UI experience for editing datatypes, calling conventions, and argument lists to be a lot nicer than IDA's. With IDA I was always stuck trying and failing to come up with a function prototype that was interpreted how I want. Ghidra has a nice editor.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.