Open dennisgbrown opened 8 months ago
Today we have the structures in "OxideData," which are a hierarchical set of dictionaries mainly, capturing the relationships between collections, binaries, functions, blocks, and instructions. Very little data is stored representing "tokens" and would have to be searched serially (slowly) at the moment.
We want to show connections or relationships between things in the binary.
For example, when a user selects a token in a disassembly or decompilation (when that capability exists) we want to show connections to that same entity in the other active visualizations.
What does the internal database / knowledge base look like in order to facilitate that scenario?