You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value of the type CS_OP_MEM changed in recent releases of Capstone. CS_OP_MEM used to have the value 3, but now it is 0x80 and can be OR'ed with other types.
However, when using these Python bindings, the values of an operand.type are not always accurate in my testing. Fetching the value of operand.type still returns 3 for memory operands in some cases, as if the updates have not propagated fully.
Example with amd64 mov instruction mov qword ptr [rbp - 0x38], r12 (prints type = 3 for the operand).
Note that these scripts also print data that only exists on memory operands and succeeds, meaning it internally has the correct memory operand values but the .type attribute is incorrectly set.
The value of the type
CS_OP_MEM
changed in recent releases of Capstone.CS_OP_MEM
used to have the value3
, but now it is0x80
and can be OR'ed with other types.capstone/bindings/python/capstone/__init__.py
Lines 429 to 431 in 1abe186
However, when using these Python bindings, the values of an operand.type are not always accurate in my testing. Fetching the value of
operand.type
still returns3
for memory operands in some cases, as if the updates have not propagated fully.Example with amd64 mov instruction
mov qword ptr [rbp - 0x38], r12
(prints type = 3 for the operand).Note that these scripts also print data that only exists on memory operands and succeeds, meaning it internally has the correct memory operand values but the .type attribute is incorrectly set.
Example with RISCV-64
c.sw a1, 0(a2)
However, in this example, AArch64's
ldr x1, [x2]
the value of the operand.type is correct - it is 0x80.The text was updated successfully, but these errors were encountered: