You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry I had a little problem with x64dbg I am not sure if this is a bug or me just being lazy so I just said report it directly.
So it's been a while since I was working on this: https://crackmes.one/crackme/64f1f7fad931496abf909535
I have a problem that when I try to use trace to log all the executed instruction in a specific interval it's just seem do not do it properly.
Again it might be just me being lazy since this one has some anti debug trick.
It's just log some instructions and then quit the program. Now on my main working settings there are lot's of BP's so I just keep landing on random places. Below is the starting instructions that suppose to get logged: 0040174C | 55 | PUSH EBP | 0040174D | 89E5 | MOV EBP, ESP | 0040174F | 83EC 38 | SUB ESP, 38 | ...
And this is my log: 0x0040174C push ebp | eax=0x2B5FFCC,ebx=0x0,ecx=0x401849,edx=401849,ebp=0x2B5FF74,esp=0x2B5FEF8 0x0040174D mov ebp, esp | eax=0x2B5FFCC,ebx=0x0,ecx=0x401849,edx=401849,ebp=0x2B5FF74,esp=0x2B5FEF4 DLL Loaded: 75810000 C:\Windows\SysWOW64\cryptsp.dll DLL Loaded: 757E0000 C:\Windows\SysWOW64\rsaenh.dll DLL Loaded: 757D0000 C:\Windows\SysWOW64\cryptbase.dll DLL Loaded: 77A90000 C:\Windows\SysWOW64\bcryptprimitives.dll DLL Loaded: 757B0000 C:\Windows\SysWOW64\bcrypt.dll Hardware breakpoint (execute) at illusion.0040174C! ...
Steps to reproduce
1.Open file, set hardware bp on 0x40174C
2.Execute program till you land on bp for the second time
3.Open Trace into clear log with command ClearLog
4.Execute trace with Log Text: 0x{p:cip} {i:cip} | eax=0x{eax},ebx=0x{ebx},ecx=0x{ecx},edx={edx},ebp=0x{ebp},esp=0x{esp} and let other fields to stay unchanged.
Attachments
Here is the interval instructions that I want to trace. file.txt
The text was updated successfully, but these errors were encountered:
ghost
added
the
bug
The issue describes a bug. It does not mean the bug has been reproduced by a developer.
label
Dec 1, 2023
Operating System
Windows 11
x64dbg Version
2023-11-18_02-28
Describe the issue
Sorry I had a little problem with x64dbg I am not sure if this is a bug or me just being lazy so I just said report it directly.
So it's been a while since I was working on this:
https://crackmes.one/crackme/64f1f7fad931496abf909535
I have a problem that when I try to use trace to log all the executed instruction in a specific interval it's just seem do not do it properly.
Again it might be just me being lazy since this one has some anti debug trick.
It's just log some instructions and then quit the program. Now on my main working settings there are lot's of BP's so I just keep landing on random places. Below is the starting instructions that suppose to get logged:
0040174C | 55 | PUSH EBP | 0040174D | 89E5 | MOV EBP, ESP | 0040174F | 83EC 38 | SUB ESP, 38 | ...
And this is my log:
0x0040174C push ebp | eax=0x2B5FFCC,ebx=0x0,ecx=0x401849,edx=401849,ebp=0x2B5FF74,esp=0x2B5FEF8 0x0040174D mov ebp, esp | eax=0x2B5FFCC,ebx=0x0,ecx=0x401849,edx=401849,ebp=0x2B5FF74,esp=0x2B5FEF4 DLL Loaded: 75810000 C:\Windows\SysWOW64\cryptsp.dll DLL Loaded: 757E0000 C:\Windows\SysWOW64\rsaenh.dll DLL Loaded: 757D0000 C:\Windows\SysWOW64\cryptbase.dll DLL Loaded: 77A90000 C:\Windows\SysWOW64\bcryptprimitives.dll DLL Loaded: 757B0000 C:\Windows\SysWOW64\bcrypt.dll Hardware breakpoint (execute) at illusion.0040174C! ...
Steps to reproduce
1.Open file, set hardware bp on 0x40174C
2.Execute program till you land on bp for the second time
3.Open Trace into clear log with command ClearLog
4.Execute trace with Log Text: 0x{p:cip} {i:cip} | eax=0x{eax},ebx=0x{ebx},ecx=0x{ecx},edx={edx},ebp=0x{ebp},esp=0x{esp} and let other fields to stay unchanged.
Attachments
Here is the interval instructions that I want to trace.
file.txt
The text was updated successfully, but these errors were encountered: