Some more notes

diff --git a/notes.org b/notes.org
index 8dd58767a4f03ecdb594a71098b326d3114ad838..182c26a180219cca7299cb3a1ed9082a62ecdb09 100644 (file)
--- a/notes.org
+++ b/notes.org
@@ -1,5 +1,9 @@
 * Disassembler Factory
 
 * Disassembler Factory
 

+How exactly does that qt plugin stuff work? We probably need some
+factory where all disassemblers can register and we can take one by
+name when opening a binary.
+

 * Data Postprocessing
 ** Cleanup Chain
 
 * Data Postprocessing
 ** Cleanup Chain
 


@@ -20,4 +24,15 @@ some data sources already present.
 We're going to store transactions in XML files and zip the result
 up. Could be facts (like the region 0xAA to 0xFF is a basic
 block), deletion of such facts or changes to the binary. These facts
 We're going to store transactions in XML files and zip the result
 up. Could be facts (like the region 0xAA to 0xFF is a basic
 block), deletion of such facts or changes to the binary. These facts

-can then be sent over XMPP to implement some multiplayer frida
+can then be sent over XMPP to implement some multiplayer frida.
+
+Ideally scripting foo would then generate such transactions which are
+stored by some transaction manager and applied to the runnign data
+structure using them as a interface everywhere.
+
+* Decompiler
+
+Do natural loop detection, build some (lispy?) intermediate code and
+"optimize" sideeffects (like flags) away from instructions where not
+needed. Then reverse-apply fancy arithmetic tricks and format it as
+normal C code.