'i' command Long execution time

[daimashi]

I have noticed that every step of the 'i' command will print an assembly code to the window, similar to using the 'printf' function once. However, when using the printf function 10000 times (i 10000), the time will become very long. I hope that when executing i 10000, the assembly code will be saved in memory, not printed to the window. After executing 10000 times, it will be saved to the txt notepad at once, which may be faster

[SinaKarvandi]

Hi,
Thanks for the issue. I got what you mean. Yes, that would be a good feature but right now we don't have any similar command that stores data for a long time (even though the user might simulate this behavior by using the 'preallocated' pools and the script engine.

Fortunately, such a storing mechanism was previously implemented in HyperDbg as non-immediate messages, but as long as I remember, I never used it for any mechanism in HyperDbg.

I am thinking about the best way of formulating this feature into HyperDbg. Maybe exporting the 'i' command (or any similar stepping command) as an event will be helpful. 🤔

Right now, if you want to immediately use this feature in HyperDbg, I think it would be easier if you could modify the source based on your needs. All you need to do is creating a loop for this function. Just make sure to not access the memory directly, instead you can use MemoryMapperReadMemorySafeOnTargetProcess to read the memory of the user-mode/kernel-mode process.