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

Bug for GleeBug when assembling? #3322

Open
Dangerfreak opened this issue Mar 12, 2024 · 0 comments
Open

Bug for GleeBug when assembling? #3322

Dangerfreak opened this issue Mar 12, 2024 · 0 comments
Labels
bug The issue describes a bug. It does not mean the bug has been reproduced by a developer. try this This issue needs to be tried by a developer to see if more information is needed.

Comments

@Dangerfreak
Copy link

This issue happens for GleeBug engine only (TitanEngine works): Open any .exe (32 or 64 bit) file and set a breakpoint (F2) at any CALL or JMP or conditional jump like JE or JNE within the code . Now run the debugger until the breakpoint is reached and press space (=assemble) to change the code exactly at this CALL/JMP, e.g. to NOP. You'll notice, that the first byte won't change. If it is a multi-byte command, only the bytes after the first byte will be changed.

Example:

  1. Code before function "Assemble" (random code):
    006EEF77 | E8 49040000 | call 6EF3C5 (breakpoint was set to this line)
  2. Press space and change the code above to NOP (checkboxes all checked to see it better)
  3. Code after function "Assemble":
    006EEF77 | E8 90909090 | call 90FF800C

The first byte (E8) is unchanged! This seems to be a bug for me.

Note: If you set the breakpoint to another command (no CALL or JUMP), it works as it should.

@mrexodia mrexodia added bug The issue describes a bug. It does not mean the bug has been reproduced by a developer. try this This issue needs to be tried by a developer to see if more information is needed. labels Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue describes a bug. It does not mean the bug has been reproduced by a developer. try this This issue needs to be tried by a developer to see if more information is needed.
Projects
None yet
Development

No branches or pull requests

2 participants