add please to sdk

Is your feature request related to a problem? Please describe.
In the current api documentation classes from external libraries are displayed with their full package name. This leaves the user to search for the documentation for the external library themselves for which they must also find the correct version number.

Describe the solution you'd like
It would be nice to have the extern

Extended Binary Coded Decimal Interchange Code (EBCDIC; /ˈɛbsɪdɪk/) is an eight-bit character encoding used mainly on IBM mainframe and IBM midrange computer operating systems. It descended from the code used with punched cards and the corresponding six-bit binary-coded decimal code used with most of IBM's computer peripherals of the late 1950s and early 196

Env:

• python 3.8
• capstone 4.0.1
• ubuntu 18.04 (WSL)

Repro:

import capstone
md = capstone.Cs(capstone.CS_ARCH_X86, capstone.CS_MODE_32)
md.detail = True

# case 1
# expected: fstcw  WORD PTR [ebp-0x4] (based on Objdump disassembly which round-trips with GNU as)
for insn in md.disasm(b"\x9B\xD9\x7D\xFC", 0):
    print(insn.address, insn.mnemonic, insn.op_str)

print(

As of GDB 8.3 RISCV is supported.hope add basic support for RISC-V

Hi,

I know I am reopening an old discussion that has been already discussed here (#1032 or #162), but this is the one thing that make miasm hard to use. So I wonder if the issue with it is :

1. Not enough time to write it ?
2. The API is changing too often too create a documentation that stays up to date ?

If it is 1, I think it should be possible to have some other people involved and

The documentation should always be in sync with the latest changes. Currently, this involves me manually building it and pushing it into an S3 bucket. That could happen automatically through CI.

Additionally, it would be great if we could display a drop-down in the doc that allows viewing documentation for older versions of Zydis as well, similar to what docs.rs does for Rust

The current CONTRIBUTING.md is more like a CODE-OF-CONDUCT.md. Which is good because now we don't have to figure out one by ourselves 😁

The CONTRIBUTING.md should only contain details for developers and non-developers on how to contribute to the project.

For devs this would mean a technical guide on how to set up the environment and a narrow explanation on which directories of the p

Our documentation site is always lagging behind as updating the docs is a non-trivial task that has to be automated. Setting up the Travis job for building wouldn't be trivial (we probably won't fit into the time constraints), but we can use GitHub actions and host a documentation builder on one of our servers. We shall update both bap documentation and Primus Lisp docs.

while creating setup.py, file hierarchy has need to be like this http://docs.python-guide.org/en/latest/writing/structure/ or not like ours :D .We must change structure this way.

we rebase a PIE ELF so it isn't based at 0. but we don't fixup the relocs accordingly. thus, C++ VFTables don't actually point to anything.

The JIT API currently just checks instruction operands and emits the instruction.

• Add simple buffer implementation to collect JIT output
• Add support for labels, and link step
• Add mprotect handling (W^X) so output JIT can be executed
• Add host ABI trampoline for calling JIT with arguments and return value

The vp instructions does not decode well.
For example:
"c5 f1 ef c9" should be decoded to "vpxor xmm1,xmm1,xmm1" (instead of "lds...").
"c5 f5 74 01" should be decoded to "vpcmpeqb ymm0,ymm1,ymmword ptr [ecx]" (instead of "lds...").

Instructions are already highlighted and it would be nice if they contain tooltips with some description or/and be clickable with URL to some documentation.

We should create a corpus of tests to verify that CFG recovery is accurate and complete, and there are no regressions.

This looks like it could be a very useful library for my use case, but the two very short examples provided give no insight into how I can use the module to extract functions from a .wasm file. Could you provide some kind of documentation for the module's methods, classes and class methods, etc. along with more comprehensive examples, so that we don't have to sift through the source code to figure