unicorn icon indicating copy to clipboard operation
unicorn copied to clipboard

Unicorn CPU emulator framework (ARM, AArch64, M68K, Mips, Sparc, PowerPC, RiscV, S390x, TriCore, X86)

Results 231 unicorn issues
Sort by recently updated
recently updated
newest added

I'm running into an issue where the cpu register state (particularly the instruction pointer) is not correct during a block callback: ``` #0 hook_block (uc=0x23c3de0, address=134513775, size=10, user_data=0x26332e0) at sim_unicorn.cpp:2614...

bug

Seeing this whilst packaging for openSUSE Tumbleweed: [unicorn200_ppc64le_test_failure.txt](https://github.com/unicorn-engine/unicorn/files/9076118/unicorn200_ppc64le_test_failure.txt)

Seeing these errors whilst packaging for openSUSE Tumbleweed: [unicorn200_armv7l.txt](https://github.com/unicorn-engine/unicorn/files/9076110/unicorn200_armv7l.txt) [unicorn200_ppc64be.txt](https://github.com/unicorn-engine/unicorn/files/9076111/unicorn200_ppc64be.txt) [unicorn200_s390x.txt](https://github.com/unicorn-engine/unicorn/files/9076114/unicorn200_s390x.txt)

bug
help wanted
stale

The following code snippet causes a segmentation fault on Ubuntu 18.04 LTS (Python 3.8.10): ``` [1] 23351 segmentation fault (core dumped) python test_min.py ``` ```Python import unicorn as uc class...

bug
poc

Host : macOS 11.6.2 Jdk : tried openjdk 8 and openjdk 11 Unicorn version : unicorn-2.0.0-rc5 Both c and python codes work fine: ```c // c uc_engine *uc; int64_t r_result;...

bug
question

Hey. I've encountered a rather weird behaviour fixed in an even weirder way and I would really love to understand what's going on. I'm using Unicorn in a .NET 6...

I'm using unicorn to emulate x86 64bit and after implementing a GDT using @sashs guide i can't seem to understand why declaring static data regions returns an unmapped error. Let's...

need poc

Hello 👋 I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@liyansong2018) has found a potential issue, which I would be eager to share with...

How do we know if the run ended by hitting the max instruction count? Could UC_QUERY be extended to include that?

question

Given that there already exists a `UC_HOOK_MEM_READ_AFTER` hook, invoked only for actually successful memory reads, shouldn't there also be `UC_HOOK_MEM_WRITE_AFTER` and `UC_HOOK_MEM_FETCH_AFTER` hooks available for hooking into only successful writes...

enhancement
question