Skip to content
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

zesarux: Double entries in history #21

Open
maziac opened this issue May 21, 2020 · 2 comments
Open

zesarux: Double entries in history #21

maziac opened this issue May 21, 2020 · 2 comments
Labels
zesarux A problem inside ZEsarUX (or most probably inside ZEsarUX)

Comments

@maziac
Copy link
Owner

maziac commented May 21, 2020

Sometimes it seems as if zesarux would execute instructions twice or at least enter them into the history twice.

zesarux_membp

Bildschirmfoto 2020-05-19 um 19 24 27

@maziac maziac added the zesarux A problem inside ZEsarUX (or most probably inside ZEsarUX) label May 21, 2020
@maziac
Copy link
Owner Author

maziac commented May 24, 2020

The same happens if calls are used instead of NOPs.
I.e. there are double entries for a call.

Bildschirmfoto 2020-05-24 um 11 13 26

** HOW OFTEN:**
I checked 5x how often this occurs. After x instructions:
31712
31719
31724
31712
317124

I did the same with the NOP loop:
15417
15417
15417
15417
15417
This is more consistent.

@maziac
Copy link
Owner Author

maziac commented May 24, 2020

double entries happen also without WPMEM being hit or even with WPMEM completely disabled (-14,-15):

Bildschirmfoto 2020-05-24 um 11 34 22

So the main problem are the double entries itself. That the read mem breakpoint is fired seems to be a side effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
zesarux A problem inside ZEsarUX (or most probably inside ZEsarUX)
Projects
None yet
Development

No branches or pull requests

1 participant