Replies: 3 comments
-
Hi, But if it matters to you, I'll add timing functions separately to the script engine, and I'll notify you on this thread. Thanks again, |
Beta Was this translation helpful? Give feedback.
-
Thanks for the response and clarification. I think this would extend the scripting interface nicely! |
Beta Was this translation helpful? Give feedback.
-
Hi I was thinking about the best approach we can implement such a feature. I think the best way to support it, is through a printf style format string. However, HyperDbg's script engine doesn't support TYPEs yet. Another approach is exporting the time via a script engine function, and the user simply uses a
Thus, I think it's better to let script engine developers finish their tasks and add support to the structure and types. After that, we can have a clean and flexible implementation of the printf-style timing. But let's have a solution for you so that you can use HyperDbg with timing format for now. Go to the source code and remove the following line : HyperDbg/hyperdbg/include/ScriptEngineEval.h Line 1747 in cb711d3 and replace it with this code: Now, compile the HyperDbg, and your result of printfs (both in eval command and in events), will be changed to : That's a dirty patch for you. I'll try to add this functionality to the HyperDbg whenever we finish supporting types in the HyperDbg's script engine. |
Beta Was this translation helpful? Give feedback.
-
Hey! This is a great project and I've been reading through the well written documentation. However, I'm trying to log time data with each print I do using the scripting engine. I've read this portion here
Is this time not exposed to the scripting engine? If not, may be a good addition to have.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions