cmp instruction does not modify its operands. Currently, cmp
variants that accept a memory operand have CS_AC_WRITE access mode
set. This commit removes CS_AC_WRITE mode from cmp variants that
have it.
* Continuous integration for fuzzing
* Simplify fuzz testing output
* Makefile for suite fuzz
* fixup
* Code review taken into acount
* More readable fuzz harness
Inputs specify only on first line the mode
* forcing capstone.pc to be generated in the same place it is installed from
* x86: fix operand access of SETE & SETNE (#1262)
* forcing capstone.pc to be generated in the same place it is installed from
The last argument should be the max size of the destination, not the
source buffer. A null byte is added to the end of the destination buffer
since strncpy only adds one if it does not truncate the source.
This fixes the -Wstringop-overflow warning on GCC.
* Remove trailing whitespace
* ~2x speedup by removing array appending
More info: https://powershell.org/2013/09/16/powershell-performance-the-operator-and-when-to-avoid-it/
* Import inline C# conditionally
Avoids errors when importing module using "-Force"
* Throw exception on missing DLL
+ use idiomatic PowerShell
* Throw exception on errors
+ use idiomatic PowerShell
* Throw exception on errors
+ use idiomatic PowerShell
* Use idiomatic PowerShell
* Fix DLL path escaping
* Add native PowerShell formatting
Instruction address will display as "0xdeadbeef" in console output, but the actual value will be stored as appropriate integer type.
This allows to use "Address" property directly in code that relies on Get-Capstone disasselbly w/o type conversion.
The original module author was using hex-strings, because when you add things in PowerShell like this: $Integer + '0xFF' , PowerShell will cast everything to the type of the first operand. And it's smart enough to cast hex-string to integer.
Example: https://github.com/FuzzySecurity/PowerShell-Suite/blob/master/Trace-Execution.ps1#L195
But this is unreliable and moreover, PowerShell has peculiar quirks when casting hex-strings: https://github.com/PowerShell/PowerShell/issues/3313
* Move Capstone init to separate function
* Add Get-CaptoneVersion function
Which resturns "version" object. Also add back erroneously deleted "return" to Get-CapstoneDisassembly -Version and convert it to advanced function.
* Fix help text
* Replace double quotes with single quotes where appropriate
* No need to assign $null to switch params
* Make return usage more obvious
* No need for double quotes in version banner
* Add space after comma
* ~3x speedup by removing New-Object usage. Requires PS 3.0
* Cosmetic fixes
* Remove PS 2.0 compatibility code
* Fix PSScriptAnalyzer warnings
* Don't load module if inline C# doesn't compile
* Return actual instruction bytes
* Fix version function
* Use lowercase for accelerators
* Remove "Mandatory = $False" since it's default
* Add spaces around "=" and ";"
* Use lowercase for built-in variables
* Tabs -> Spaces
* Update help
* Use standard manifest
* UTF-8, no BOM
* Remove remaining New-Object invocations
* Bump module version (semver anyone?)
* Restore PSv2 compatibility
Use [pscustomobject]/New-Object based on reported PS version.
* Tabs -> Spaces
* Update authors
* arch/TMS320C64x: fix underflow
(patch coming from radare2)
* arch/TMS320C64x: fix spaces between if/for/while and parenthesis
* arch/TMS320C64x: switch back to ==
