arno/bddisasm
1
0
Fork 0
mirror of https://github.com/bitdefender/bddisasm.git synced 2024-11-22 15:38:07 +00:00
Code Issues Releases Wiki Activity
0b7c9a84fe
bddisasm/bddisasm_test
History
Andrei Vlad LUTAS 94d7894fa5 Added the Shadow Stack Pointer operand to the SYSRET and SYSENTER instructions. 
Regenrated CET test files, as the CPUID feature flag was split as per the last documentation into CET_SS and CET_IBT.
2020-07-22 09:15:29 +03:00
..
amx Initial commit. 2020-07-21 11:19:18 +03:00
avx Initial commit. 2020-07-21 11:19:18 +03:00
avx512 Initial commit. 2020-07-21 11:19:18 +03:00
basic Added the Shadow Stack Pointer operand to the SYSRET and SYSENTER instructions. 2020-07-22 09:15:29 +03:00
cet Added the Shadow Stack Pointer operand to the SYSRET and SYSENTER instructions. 2020-07-22 09:15:29 +03:00
simd Initial commit. 2020-07-21 11:19:18 +03:00
special Added the Shadow Stack Pointer operand to the SYSRET and SYSENTER instructions. 2020-07-22 09:15:29 +03:00
README.md Initial commit. 2020-07-21 11:19:18 +03:00
test_all.py Initial commit. 2020-07-21 11:19:18 +03:00

README.md

Disassembler Tests

These tests are used to validate bddisasm. Each test consists of up to three files:

  • The binary test file. The name format for this type of file is name_16|32|64. No extension must be provided; 16/32/64 indicates disassembly mode
  • The output result file. Must be named the same as the binary test file, but with the extension .result
  • Optional assembly file, used to generate the binary test file

The test_all.py script will iterate all the test folders, and it will run bddisasm on each identified test file. The result file will be compared with the output of the test run. If they are not the same, the test will fail. Note that bddisasm will be run with the -exi option, in order to dump all possible information about the instructions.

NOTE: This test will assume disasm is in the path. Works on Windows only.