-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test function is quit expensive #10
Comments
If you think that having the possibility to insert an hook just before calling emu_cpu_step (line 592) could be beneficial for your purposes I can easily add this feature for your convenience. Thinking about something like
[..]
Maybe I need to think about details but think that this approach could easily allow you to subclass Emulator and define your own hook(s). Please let me know if it could be ok for you. |
cython complain but if you can find a way to solve that, please add break if return for self.test_hook(self._emu) is True
|
Hi Angelo, |
Hi,
currently, my work need me to call test repeatedly
for i in range(x):
#do something
pylibemu.Emulator().test(1)
#continue do something
if x less than 5000, its working fine. But when x getting bigger, such as 1000000, my whole desktop freeze :)
looking at test() implementation, it seem quite expensive.
Is it possible to expose/wrap all needed variable to allow my code instrument emu_cpu_parse() and emu_cpu_step() so it wont using the built in function test()?
or if possible add callback function in test(), so I can execute my function in each loop before execute emu_cpu_step().
The text was updated successfully, but these errors were encountered: