Chen

> I could not reproduce the segfault with Python 3.13. Only with Python 3.12. I am not sure if we should merge this without this segfault being fixed. Probably not....

Quite a lot errors generated in `*.inc`: ```log [17/212] Building C object CMakeFiles/cap.../AArch64/AArch64DisassemblerExtension.c.o FAILED: CMakeFiles/capstone.dir/arch/AArch64/AArch64DisassemblerExtension.c.o /usr/bin/cc -DCAPSTONE_AARCH64_SUPPORT -DCAPSTONE_ALPHA_SUPPORT -DCAPSTONE_ARC_SUPPORT -DCAPSTONE_ARM_SUPPORT -DCAPSTONE_BPF_SUPPORT -DCAPSTONE_DEBUG -DCAPSTONE_EVM_SUPPORT -DCAPSTONE_HAS_AARCH64 -DCAPSTONE_HAS_ALPHA -DCAPSTONE_HAS_ARC -DCAPSTONE_HAS_ARM -DCAPSTONE_HAS_BPF -DCAPSTONE_HAS_EVM -DCAPSTONE_HAS_HPPA...

> thank you for creating the amazing Mac App „MacGesture“, which is an indispensable tool for me and which I use daily. I wanted to ask, whether the App is...

> Or is API stability more important for everyone and we just keep it as is? > How about type alias e.g. typedef or define?

SONAME changed, please bump reverse dependencies

The Vivado part is, you need to setup to project using digilent-vivado-scripts, open Vivado project, generate bitstream, program the bitstream to FPGA until you see `NO BOOT FAIL` on the...

That's quite interesting... So basically, `fstox %f0, %f4` reads f0 and writes to f4 & f5; `fqtoi %f0, %f4` reads f0-f3 and writes to f4.

There is a small place where the existing `disasm_all/disasm_count` is more convenient: `disasm_iter` does not allow having two `Insn` at the same time (due to sharing their details pointer).

> There is a small place where the existing `disasm_all/disasm_count` is more convenient: `disasm_iter` does not allow having two `Insn` at the same time (due to sharing their details pointer)....

AARCH64 cbr instrumentation done in pr https://github.com/DynamoRIO/dynamorio/pull/7005. Please test and report issues if any. I am re-opening this issue since ARM cbr instrumentation is not implemented yet.