juliapoo / este Goto Github PK

E.g. in WOW64, logging every execution of heaven's gate messes up the graph.

1. Refactor existing python scripts
2. Write a python wrapper over Este PINTOOL
3. Figure out build toolchain

1. Halves the number of locations PIN needs to instrument and
2. Removes the costly procCtx->getBbIdx(bbl_addr) call in BblAft

Am thinking to set the timeout to be smaller, but give the option to reheat the physics engine

1. .bb.csv: Ensure basic blocks are unique and idx is consecutive
2. .trace.csv: Ensure all the jumps between the basic blocks are plausible (need to disassemble each bb)

Search for API calls and addresses.

User controlled parameters

1. Whitelist of which binaries to log control flow from

Information to extract from binary during runtime:

1. General Information

• PID, Process name
• Binaries loaded and the address range of their executable sections

2. General Control Flow

• Address range of basic blocks* encountered and TID associated

3. Basic blocks*

• Address range of basic block
• Bytes of basic blocks encountered
• Binary basic block is located in
• Routines* outside of whitelist that's called within basic block

3. Routines*

• Address range of routine
• If symbol available, name of symbol
• Which binary routine is located in