Interesting Log Breakpoints
`
Software Log Text
00418D10 ##########Setting {s:[esp +4]} = 0x{x:[esp + 8]}
00946140 #########endingfunc1 called, arg1={d:[esp + 4]}, arg2={d:[esp + 8]}, arg3={d:[esp + C]}
00A7C800 ##########text = {s:[esp + C]}
00AF43C0 ##########CryptArc4Apply called! Addr:0x{x:[esp + 8]}, Size:0x{x:[esp + C]} = {mem;[esp + C]@[esp + 8]}
00B05557 ##########closing something, ebp = {x:ebp}, [ebp + 4] = {x:[ebp +4]}
00B05580 ##########cleanup calling 0x{eax}
00BF0270 ##########finish it!
00BF037A ##########finish with 7!
00BF0785 ##########lower end
00BF08D1 ##########upper end
00BF09FE ##########awaits http = {x:[eax+0x108C]}
00BF0A41 ##########recv with {d:eax}
00BF0A7B ##########statePlaceA is {d:eax}
00BF0AE7 ##########main end, eax = {eax}
00BF0B7B ##########state PlaceB is {d:eax}
00BF0F0C ##########closing reason = {x:[ecx+0x128]}#########`
Example Log for CryptArc4Apply
add these to the debugger x32dbg (ofc if ALSR is removed!) when attaching to the server. when editing, enter like this:
Set breakcondition to 0 and log condition to 1 to only produce logs