farmdve

@lunixbochs In this case, both hooks will be called again. The REP STOS instruction is jitted to regular movs and a call to a qemu handler to store the data...

I should probably mention the following. The way I've made the changes is, I've added an additional argument to the hooks, this means all projects that use UC_HOOK_CODE will need...

@aquynh I see, ok. However my changes do not break uc_hook_add, they change the callback parameters to add one additional argument. But they still break existing code yes. ``` c...

Because a user will not know what type of hook it is. And no, it's not possible to track them, because the post instruction hook may not be called if...

If it's two user callbacks uc_hook_add(PreCallback); uc_hook_add(PostCallback); Then yes.

Then, I'll have it rework it. Meanwhile, this is unrelated but I plan to launch an online emulation platform to test out Unicorn. This way I can more easily show...

Because of the post instruction hook, and depending on whether either are active or both, the argument patching for instruction size(for the pre hook) has become more difficult, and I...

Here is the commit. Although git pushed to my master rather than new branch :/ https://github.com/farmdve/unicorn/commit/6648e41ab987bbf46301e1458fa1d4a169cae1df I tested the code as much as I could, this is why it took...

Sure, ok. Will do it tomorrow though. In the meantime, all is well, but like I said, REP prefixed instructions, due to the way they are jitted will cause the...

Personally, I believe we should monitor all instructions. Even when single-stepping in a debugger, the REP prefixed instruction executes as many times as they need without EIP changing. And yes,...