support disassembling bytes from memoryview #1758
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* 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.
* Fix typos * make test_mos65xx.py and test_mos65xx.c have same output format * mox65xx -> mos65xx
* respect libsuffix in pkgconfig discovered in https://bugs.gentoo.org/677946 * Update CMakeLists.txt * Update CMakeLists.txt * Update CMakeLists.txt
* fix mode "c" in report_cstest
…ne-engine#1402) Signed-off-by: Sebastian Macke <sebastian@macke.de>
* add xenial tests * add cmocka remove reminder
* normalize tab character in cs
* normalize tab character in cs * normalize in issue mode
…engine#1423) * AArch64: fixes register access flags for loads * AArch64: fixes register access flags for ORR * AArch64: fixes register access flags for stores
Signed-off-by: Sebastian Macke <sebastian@macke.de>
Pass bytearrays by reference instead of copying to bytes.
…default (capstone-engine#1463) * Add cmake option to disable architectures by default * Add cmake option to disable architectures by default * Remove CAPSTONE_X86_ONLY cmake variable, and update build scripts to use the CAPSTONE_ARCHITECUTRE_DEFAULT option, which can be used with any architecture. * Updated cmake and nmake files to replace cmake-x86 and nmake-x86 * Simplified cmake wrapper scripts * Updated cmake build instructions * Tab to space in doc
* Fix user data alignment in MEMBLOCK Kernel memory allocations on Windows should be aligned on MEMORY_ALLOCATION_ALIGNMENT (16 bytes on x64 and 8 bytes on x86). * Fix user data alignment in CS_WINKERNEL_MEMBLOCK
Apple Clang 11.0.0 error:
```
capstone/include/capstone/m68k.h:160:3: error: anonymous types declared in an anonymous union are an extension [-Werror,-Wnested-anon-types]
struct { ///< register pair in one operand
^
```
Co-authored-by: Romain Lesteven <romain.lesteven@armaturetech.com>
* Add __repr__ for capstone.CsInsn Currently, a `print(instruction)` displays a not very useful string like `<capstone.CsInsn object at 0x7f3759d88128>`. This PR enhances adds a `__repr__` magic method to the `capstone.CsInsn` class so it displays as follows: ``` <cs.CsInsn: address=0x5555555545fa, size=1, mnemonic=push, op_str=rbp> ``` * Update __init__.py
$(PYTHON2) and/or $(PYTHON3) might differ from python and/or python3, accordingly. Allow to override these variables by user choice.
…1659) On x86_64-linux gentoo system capstone was installing it's files to 'lib64' libdir, but was referring 'lib' libdir: ``` $ cat /usr/lib64/pkgconfig/capstone.pc ... libdir=${prefix}/lib ... ``` On radare2 built it means injecting -L/usr/lib into a 64-build and pulling in 32-bit libraries. 'ld.lld' is not able to resolve the ambiguity. It happens because @LIBSUFFIX@ is not present in cmake-3.17.3. Let's fix the paths by using @CMAKE_INSTALL_LIBDIR@. This variable is already used in capstone's build system, thus should be safe to rely on. Reported-by: Agostino Sarubbo Bug: https://bugs.gentoo.org/730722 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
instructions could be 2, 4 or 6 bytes so pad accordingly as it was done on the other CISC architecture.
if integer is 32-bit, and numeric literals default to int type, the following applies (from The C Standard, 6.5.7, paragraph 4 [ISO/IEC 9899:2011]): If E1 has a signed type and nonnegative value, and E1 × 2^E2 is representable in the result type, then that is the resulting value; otherwise, the behavior is undefined. which means that the only way to safely shift is unsigned, so use 1U to indicate the shifted bit is unsigned.
Co-authored-by: meme <meme@users.noreply.github.com>
Otherwise python setup.py install from bindings/python will fail with SyntaxError: Non-ASCII character '\xe2' in file setup.py on line 223, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
Co-authored-by: Michal Schulz <michal@Michals-iMac-Pro.local>
Co-authored-by: Raffaele Meyer <Raffaele Meyer>
* Update solution, remove non-existent test_basic * Add property sheet to set platform toolset correctly * use property sheet in all projects * cast explicitly to avoid warnings * make property sheet optional * Conflcting options "Edit and continue" and "optref" caused warnings Co-authored-by: Hauke Mönck <>
Signed-off-by: Tomasz 'CeDeROM' CEDRO <tomek@cedro.info>
With FreeBSD, OpenBSD, NetBSD verified we can simply use "bsd". Signed-off-by: Tomasz 'CeDeROM' CEDRO <tomek@cedro.info>
|
can you pull req to the next branch? |
|
Looks like I have to close this so I can open a new PR from my own next branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there! I am not sure about the rules for contributing, please let me know if this should go to a different branch. I am working on a project where I want to create a lot of
memoryviewslices and pass them to the disassembler; slicingbytearrays is always an O(n) copy, while slicing thememoryviews is O(1). This simple adjustment for the type check adds support for that.