Choongwoo Han

it's broken in pip-installed version (3.0.4) of capstone, but seems it's fixed in the master branch of capstone.

Appreciate your interest. But, I'm currently not maintaining this code. I recommend you to use [afl-fuzz](http://lcamtuf.coredump.cx/afl/). It's much more improved now, and most features in afl-fuzz-js are also supported by...

I think you need to run `python setup.py build` to build the libqsym.so file. It works for me.

yes, it seems like `pip install .` works well.

I'm currently using only ALE. I've never tried to use both of ALE and syntastic at the same time. I guess users should disable one of ALE or syntastic.

@wsdjeg then why do we have *syntastic* support in this repo? not all vim-fsharp users use syntastic. this repository implemented interactions with *fsautocomplete* to find errors of codes, and this...

@kjnilsson FYI, I don't have any problem even when both of ale and syntastic are installed at the same time. Each of them works well.

I have the same issue. It was indeed a CFG issue. When, `longjmp` is called, the `longjmp` function in `VCRUNTIME140.dll` is called, which has CFG enabled. And, if `Frame` is...

Here is a snippet of profiling. Profiled by WPR and tested on Windows. Dev branch ``` - helper_le_stq_mmu_x86_64 (68.38%) - store_helper (67.94%) - notdirty_write (33.63%) - page_collection_lock_x86_64 (30.94%) - _malloc_base...

Oh, thanks for the hint. Now I see this problem: Unicorn always returns `false` for `cpu_physical_memory_get_dirty` and `true` for `cpu_physical_memory_is_clean`. So, `tlb_set_dirty` is never called in `notdirty_write`, and Unicorn always...