sushant94/esil-tests

Automated Testing for errors in ESIL emulation

esil-tests's Issues

[Discuss] Integration with radare2 tests

Some important points to discuss:

• Do we want to run these tests on every r2 push? This may not be helpful as this test is bound to be marked as pass each time.
• How do we determine failure? Right now, we have about 3000 Mismatches (I'm sure some of them are false positives). So until this number goes down, we cannot make this test fail if we're planning to run it with radare2 tests.
• Including this as a part of r2 tests will increase the test time substantially. Do we need this?
• If we decide not to run this as a part of r2 tests. When do we run this?

Include serial number in logs

Helps reference/discuss about a bug in specific

Add NOSUDO option

Also, don't check if 'TRAVIS' - pls add an option too to run gdb.

/tmp/t

t

[Discuss] Triage Module

Implement a triage module with convenient methods to parse and work with the log generated. Some options to mark certain elements of logs as valid/invalid/important and automatically exporting these to raise issue on Github would be nice too. More discussion on features are welcome.

Port to src/tracer.py to LLDB

[ESIL Emulation] r13d set incorrectly

Binary: Ubuntu 14.04 - /bin/ls
Instruction: mov r13d, edi
ESIL: rdi,r13d,=
Offset: 0x411733

REGISTER	GDB	ESIL
r13	0x7fffffffe050 -> 0x1	0x7fffffffe050 -> 0x7fff00000001

Include Binary files in log

Export binary file used in testing as a base64 encoded string from travis to help reproduce and inspect tests.

Testing GHI

Test Issue. Will close.

Populate stats for analysis

Some statistics of interest, such as:

• Time
• Number of instructions executed (by tracer and emulation)
• Number of invalid ESIL instructions
• Number of TODO encountered
• opcodes unimplemented ordered based on frequency of occurrence
• Number of corrections made

should be logged.