Capstone disassembly/disassembler framework: Core (Arm, Arm64, BPF, EVM, M68K, M680X, MOS65xx, Mips, PPC, RISCV, Sparc, SystemZ, TMS320C64x, Web Assembly, X86, X86_64, XCore) + bindings. (bloaty 依赖)
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.
 
 
 
 
 
 
Nguyen Anh Quynh e29eaf9cbb tests: use LDFLAGS to link test files - this is to make Gentoo happy 11 years ago
..
Makefile tests: use LDFLAGS to link test files - this is to make Gentoo happy 11 years ago
README initial import 11 years ago
test.c fix for the last commit, and make the test code no longer specify ppc code as 64bit 11 years ago
test_arm.c rename API cs_disasm_dyn() to cs_disasm_ex(), and intentionally breaks compatibility with 1.0 11 years ago
test_arm64.c rename API cs_disasm_dyn() to cs_disasm_ex(), and intentionally breaks compatibility with 1.0 11 years ago
test_detail.c rename API cs_disasm_dyn() to cs_disasm_ex(), and intentionally breaks compatibility with 1.0 11 years ago
test_mips.c rename API cs_disasm_dyn() to cs_disasm_ex(), and intentionally breaks compatibility with 1.0 11 years ago
test_x86.c rename API cs_disasm_dyn() to cs_disasm_ex(), and intentionally breaks compatibility with 1.0 11 years ago

README

This directory contains some test code to show how to use Capstone API.

- test.c
This code shows the most simple form of API where we only want to get basic
information out of disassembled instruction, such as address, mnemonic and
operand string.

- test_detail.c:
This code shows how to access to architecture-neutral information in disassembled
instructions, such as implicit registers read/written, or groups of instructions
that this instruction belong to.

- test_<arch>.c
These code show how to access architecture-specific information for each
architecture.