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 'master'
${ noResults }
bddisasm/bdshemu_test
History
Andrei Vlad LUTAS 37a8c94bc7
Applied some of the syntax recomandations from https://cdrdv2.intel.com/v1/dl/getContent/817241. 		2 months ago
..
x86 Applied some of the syntax recomandations from https://cdrdv2.intel.com/v1/dl/getContent/817241. 2 months ago
README.md BDDISASM v2.1.0 release - please consult the CHANGELOG for details about the modifications. 2 months ago
test_all.py BDDISASM v2.1.0 release - please consult the CHANGELOG for details about the modifications. 2 months ago

README.md

Shellcode Emulator Tests

These tests are used to validate basic bdshemu functionality. Each test consists of up to three files:

  • The binary test file. The name format for this type of file is name_32|64[_r0].test. 32 indicates 32 bit test file, 64 indicates 64 bit test file, and r0 indicates kernel payload
  • 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 bdshemu 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: This test will assume disasm is in the path. Works on Windows only.