• Reading binary data (.data section)
• Reading and parsing instructions (.text section)

Use readelf/objdump and a lookup table. RISCV is easy, every instruction is 32 bits!

The "emulator" #3 will also output a number of constraints which continuously need to be solved.

• Figure out a representation of constraints which the "emulator" will output

• Large hashmap mapping addresses to values/symbols
• Possibly also include registers in this structure

Instructions need to be classified as:

• Branching
• Conditional branching (here the symbolic executor needs to fork)
• Writing to memory (mutually exclusive with reading to memory AFAIK, check this). Not mutually exclusive with branches/conditional branches
• Reading from memory (mutually exclusive with writing to memory AFAIK, check this). Not mutually exclusive with branches/conditional branches
• Possibly see register accesses as memory, or at least make it part of the memory storage system since registers can also just contain variables and symbolic variables

Don't forget that code is also part of memory and technically readable. This forms part of a number of exploits so needs to be taken into account

Sicco suggested we should do it to have a nice start for the report.

Emulate OS:
User I/O (input)
File system