Skip to content

Next#1

Merged
keenk merged 1261 commits intokeenk:nextfrom
capstone-engine:next
Jun 29, 2019
Merged

Next#1
keenk merged 1261 commits intokeenk:nextfrom
capstone-engine:next

Conversation

@keenk
Copy link
Copy Markdown
Owner

@keenk keenk commented Jun 29, 2019

No description provided.

aquynh and others added 30 commits February 14, 2019 01:30
* fixing

* Done fixing
* Comment out all failed tests
* Integrate with Travis
* cstest: partial details are supported in issues.cs
* Avoids overflow in getRegisterName for TMS320C64x

* Revert "Avoids overflow in getRegisterName for TMS320C64x"

This reverts commit 18acee6.

* Checks register in DecodeMemOperandSc
For the peace and tranquility of the earth.
* Basic changes of new arch - BPF

* Define some constants

* defined some API methods

* Able to print MISC instruction

* Follow Linux coding style

* Ability to show ALU insn names

* decode return

* Add suite/MC/BPF

* decode jump

* decode store

* decode load

* print instruction done

* try to implement BPF_reg_access

* Implements explicit accessed registers and fix some tiny bugs

* Fix unhandled ja case

* Added BPF_REG_OFF do fix wrong display in jump class

* Great I'm able to decode cBPF with eyes

* Fix: misunderstood the 16-byte instruction's imm

* Add ldxdw

* Add extended-all.cs

* Implements cstest/bpf_getdetail.c

* Fix memory leak

* Add BPF to fuzz

* Implemented regs_read and regs_write

* Fix missing write-access on ALU's dst

* Updated cstool/, test_basic.c, test_detail.c, and test_iter.c

* Updated docs

* Fix type of cs_bpf#operands

* Implements python bindings

* Fix some bugs found by self code review

* Remove dummy tests

* remove typeof

* Address comments

* Fix MSVC's warnings and add test_bpf.py to bindings/python/Makefile

* Fix: call is not offset
aquynh and others added 26 commits May 14, 2019 10:59
sets CS_AC_READ for memory operand of call and jmp instructions
there are clearly 7 options, not 5 options. just updating the numbers.
EditorConfig should help us maintain consistent style across different
editors. Many editors have native support; others have plugins.

Website: https://editorconfig.org/
- This is not suitable for an application framework
  especially for kernel code.
- All these error conditions do not occur under normal conditions.
  They only can occur if a maintainer (in the future) would make
  inappropriate changes to the M680X code base.
- Added CS_ASSERT macro which allows to use assertions when debugging
  by defining CAPSTONE_DEBUG.
- Updated compiler documenation
* makefile: set CAPSTONE_DEBUG for debug build

Also fix long longs

* riscv: replace assert with CS_ASSERT

* cmake: add CAPSTONE_DEBUG option
* updated 6502 support. some improvements to the base 6502 support but also adds support for 65c02, w65c02, and 65816.

* add CS_OPT_SYNTAX_MOTOROLA.

This will use "$" as a hex prefix instead of "0x"

* remove excess blank lines
@keenk keenk merged commit 02f4a04 into keenk:next Jun 29, 2019
keenk pushed a commit that referenced this pull request Jun 29, 2019
* Fixes capstone-engine#1317 - arm thb operand.shift.value

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 #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
keenk pushed a commit that referenced this pull request May 5, 2023
keenk pushed a commit that referenced this pull request May 5, 2023
Add handling of prefix `NOTRACK`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.