mirror of
https://github.com/bitdefender/bddisasm.git
synced 2024-11-22 15:38:07 +00:00
9ff2543660
Moved the CET test cases in dedicated folders. Improved shadow-stack operand reporting - a distinction can be made between push/pop shadow stack accesses, and other shadow stack accesses. A new field is now present in the memory information - the shadow stack access type, which indicates: explicit access, implicit via SSP, implicit push/pop via SSP or implicit via IA32_PL0_SSP. |
||
---|---|---|
.. | ||
amx | ||
avx | ||
avx512 | ||
basic | ||
cet | ||
simd | ||
special | ||
README.md | ||
test_all.py |
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.