.Dear friends,
I have recently finished a Debugger for Windows 64 bits, still it is a very simple debugger, but it has some features that neither IDA nor OllyDbg nor WinDbg have, like debug multiple processes and debug multiple child processes, but may be the most interesting feature is the �Detour� utility. The actual disadvantage is that only debugs 64 bits software, but it is a long term project and surely in a close future 64 bits software will be more common.
Being brief, this post is to request help with testing the release candidate version of the debugger
Link: www.duxcore.com
There is no help documentation yet, but the user interface is very intuitive and if you have any doubt you could watch some tutorials videos.
- Basic (Create - Attach - Detach - Terminate)
http://www.youtube.com/watch?v=2qM04zD9-LQ
- Breakpoints (SW Breakpoints - HW Breakpoints - Wnd Frame Information)
http://www.youtube.com/watch?v=RYutHass7_o
- Detours
http://www.youtube.com/watch?v=3ubvshqJViU
Detour explanation:
When the debugger reaches to a target function automatically the debugger redirects the control to a detour function, previously you have to load your own modules (.dll .exe).
In the SDK directory there are some samples of how you must write detours functions.
To make testing simpler, I provide a compiled dll sample, with a function �Duxrand� that always return a same number, so if you debug Minesweeper with the detour, you will see that mines are not random.
Target Function -> msvcrt.dll -> rand
Detour Function -> DuxDbgClient.dll -> Duxrand
I would appreciate errors notifications, suggests, etc., remember that is the first version so it is very simple!
[email protected]
Thank you very much!
I apologize for any language mistake, English it�s not my native language.
![[+] expand](/imagery/files/soysauce_blueprint.gif){kind=link}