arno
/
bddisasm
mirror of https://github.com/bitdefender/bddisasm.git
1
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9ff2543660'
${ noResults }
bddisasm/bddisasm_test
History
Andrei Vlad LUTAS 9ff2543660
Added the Shadow Stack Pointer operand to the SYSCALL and SYSEXIT instructions. 		4 years ago
..
amx Initial commit. 4 years ago
avx Initial commit. 4 years ago
avx512 Initial commit. 4 years ago
basic Added the Shadow Stack Pointer operand to the SYSCALL and SYSEXIT instructions. 4 years ago
cet Added the Shadow Stack Pointer operand to the SYSCALL and SYSEXIT instructions. 4 years ago
simd Initial commit. 4 years ago
special Added the Shadow Stack Pointer operand to the SYSCALL and SYSEXIT instructions. 4 years ago
README.md Initial commit. 4 years ago
test_all.py Initial commit. 4 years ago

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.