-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
preparations for python3, added pythonic critiques, added python idioms. #1
Conversation
these are untested, but I believe still valie.
Another note on python3, the import is broken
|
Grugq, this file was actually orphan file, and got deleted. but i will however, you have this:
def op_count(self, op_type): this is not what it means: op_count() doesn't return the length of <--- pay attention to the 2nd param. for example, to count the number of register operands in current arm
otherwise, of course you want len(insn.operands) to get the number of cheers, On Wed, Nov 27, 2013 at 4:13 PM, thaddeus t. grugq <[email protected]
|
Also fixed compact parsing of colors without quotes.
Fixed OSX chdir #if line
Merging fungos changes into fork.
For a more detailed description, see issue capstone-engine#1317. Release 4.0.0 introduced a new field for ARM operands: `operand.mem.lshift`. This field was supposed to be a bug fix for capstone-engine#246. The capstone-engine#246 issue has been fixed in the meantime and the proper shift value was stored in `operand.shift.value`. The 4.0.0 changes created a regression in which `operand.shift.value` was not set for a `tbh [r0, r1, lsl capstone-engine#1]` instruction on ARM and the value was set in a `operand.mem.lshift` field instead. As the regression broke some of users codebase (e.g. in [manticore](trailofbits/manticore#1312) project), we fix it by setting `operand.shift.value` back again. As a result, the shift value is set in two fields: `operand.shift.value` and `operand.mem.lshift`. As the `operand.shift` also stores a `.type` field, we might want to deprecate `operand.mem.lshift` in the future.
* Fixes #1317 - arm thb operand.shift.value For a more detailed description, see issue #1317. Release 4.0.0 introduced a new field for ARM operands: `operand.mem.lshift`. This field was supposed to be a bug fix for #246. The #246 issue has been fixed in the meantime and the proper shift value was stored in `operand.shift.value`. The 4.0.0 changes created a regression in which `operand.shift.value` was not set for a `tbh [r0, r1, lsl #1]` instruction on ARM and the value was set in a `operand.mem.lshift` field instead. As the regression broke some of users codebase (e.g. in [manticore](trailofbits/manticore#1312) project), we fix it by setting `operand.shift.value` back again. As a result, the shift value is set in two fields: `operand.shift.value` and `operand.mem.lshift`. As the `operand.shift` also stores a `.type` field, we might want to deprecate `operand.mem.lshift` in the future. * Add changelog stub
…t-next fix bug in displacement offset
Add handling of prefix `NOTRACK`
these are untested, but I believe still valid.