Roadmap
Quokka is not perfect and some features could be improved.
The list below is not a Roadmap per se but more like a wishlist.
Do not hesitate to open Issues for requesting features.
Export Information
- Types Information
Quokka now exports type information (structures, enumerations, unions, arrays, pointers). See Types.
- Stack Variable
IDA defines stack variables in the function. Exporting them could be valuable for some workflows
- Decompiler
Hex-Rays generates a pseudo C-code from binary code. Quokka can now optionally export this pseudocode (see Decompilation).
- Operands Data
While the operands are exported, it is hard to understand them outside IDA without having the disassembler documentation. Exporting information on them could be interesting.
Refactor
-
Rewrite the Reference Manager
The
Reference Manageris hard to understand, to maintain and to use. Plus, it has some performance issues. It has to be rewritten to be improved while not losing any functionalities. -
Remove the interface for Function Chunks
A Function Chunk is an IDA abstraction for function parts. However, it is meaningless to expose them in the user interface because users do not care about them.
-
Use
weakreffor ProgramProgramhas backrefs in most items inQuokka. However, we should useweakrefto allow the garbage collector to do its magic when cleaning some parts of the program.
Disassemblers
- Quokka for Ghidra
Ghidra is now supported via a dedicated extension (>= 12.0.3). See Installation.
- Quokka for Binary Ninja
Some researchers have moved to Binary Ninja. Having an export working for Binary Ninja could help Quokka adoption.
Misc
- Support Fat binaries
IDA supports disassembling Fat Binaries but Quokka will only export the first one. One nice feature would be to select which one to export
- Verify the support for unknown architectures
Quokka should export any binary but it has been barely tested with other architectures.