Fork 0
An open-source x64/x32 debugger for windows. Official mirror for China: https://github.com/x64dbg/x64dbg
Go to file
Mr. eXoDia 8c24955031 DBG: removed DeviceNameResolver (bug was fixed by ahmadmansoor already)
PROJECT: updated release script
2014-04-17 20:18:01 +02:00
bin PROJECT: updated BeaEngine (r8L -> r8b) 2014-02-22 15:34:34 +01:00
help DBG: added the detach command (should be working now) 2014-04-16 20:30:15 +02:00
x64_dbg_bridge BRIDGE: updated internal version number 2014-04-17 00:43:42 +02:00
x64_dbg_dbg DBG: removed DeviceNameResolver (bug was fixed by ahmadmansoor already) 2014-04-17 20:18:01 +02:00
x64_dbg_exe PROJECT: added Guids for the visual studio projects 2014-02-22 22:19:57 +01:00
x64_dbg_gui/Project DBG: added EnableDebugPrivilege setting 2014-04-16 19:25:45 +02:00
.gitignore PROJECT: updated gitignore 2014-04-17 00:34:37 +02:00
bug.ico first commit 2013-11-14 21:55:18 +01:00
clean.bat PROJECT: updated clean.bat 2013-12-06 15:10:44 +01:00
readme.txt PROJECT: updated readme 2014-03-03 01:24:16 +01:00
release.bat DBG: removed DeviceNameResolver (bug was fixed by ahmadmansoor already) 2014-04-17 20:18:01 +02:00
todo_dbg.txt PROJECT: updated todo list 2014-03-30 14:47:56 +02:00
x64_dbg.sln PROJECT: added solution dependencies (thanks to iLovro) 2014-03-02 01:08:18 +01:00
x64_dbg.workspace PROJECT: removed crash dumper 2014-02-18 20:03:16 +01:00
x64_dbg_sceme.vsd PROJECT: added design 2014-03-18 20:52:40 +01:00


[This is a new version of this repository. The old version can be found ]
[here: https://bitbucket.org/mrexodia/x64_dbg_old                       ]

>Installation guide:
1) Download the latest 'qt_base_XXX.rar'
2) Download the latest 'bin_base_XXX.rar'
3) Download the latest 'release_xxx.rar'
4) (Optional) Download the latest 'help_XXX.rar'
5) Extract all in the same directory
6) Run 'bin\x64\x64_dbg.exe' or 'bin\x32\x32_dbg.exe'

This is a x64/x32 debugger that is currently in active development.

The debugger has (currently) three parts:
- Bridge

DBG is the debugging part of the debugger. It handles debugging (using
TitanEngine) and will provide data for the GUI.

GUI is the graphical part of the debugger. It is built on top of Qt and it
provides the user interaction, the dump window (not yet implemented), the
disassembly, the register window, the memory map view, the log view etc.

Bridge is the communication library for the DBG and GUI part (and maybe in
the future more parts). The bridge can be used to work on new features,
without having to update the code of the other parts.

- variables (with regard to the upcoming script feature)
- basic calculations (var*@401000+.45^4A)
- hide debugger (very basic)
- software breakpoints (INT3, LONG INT3, UD2)
- memory breakpoints (read, write, execute)
- hardware breakpoints (access, write, execute)
- stepping (into, over, n instructions)
- rtr (return from function)
- memory allocation/deallocation in the debuggee
- quickly accessing API addresses (GetProcAddress->76E13620)
- highlighting (not yet customizable, but really helpful)
- memory map
- basic module labeling
- import reconstruction (plugin using Scylla)
- drag&drop files
- goto window
- register/flags view with editing support
- quite fast working in really big code pages (tested up to 5GB)
- GUI hotkeys
- dynamic jump arrow (just like OllyDbg)
- user databases for labels/comments/breakpoints/bookmarks (*.dd64 or *.dd32 files)
- easy context menu in disassembly (to set breakpoints etc)
- plugin support
- (manual) function analysis
- easily follow calls/jumps/ret (press ENTER when selecting)
- (buggy) dynamic commenting
- scripting support (using the debugger commands)!
- simple dump
- symbols (+ exports) view with search
- simple stack view
- programmable reference view

>Known bugs:
- memory breakpoints sometimes fail (TitanEngine bug)

>Last words:
The debugger core is based on TitanEngine (an updated version,

Disassembly powered by BeaEngine (http://beaengine.org/).

The icon is taken from VisualPharm (http://www.visualpharm.com/)

>Special thanks:
- acidflash
- Ahmadmansoor
- cyberbob
- Teddy Rogers
- EXETools community
- Tuts4You community
- DMichael
- Sorry if I forgot you!

>Lead developers:
- Mr. eXoDia
- Sigma