x64dbg
2025.08.19 #3689
mrexodia
announced in
Announcements
2025.08.19
#3689
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
August 2025: Bug fixes and stability
This release has mostly been focused on fixing bugs and improving stability over the long term.
🐛 Bugs
The migration to Visual Studio 2022 unfortunately caused some serious issues to slip through. The following bugs were fixed:
To prevent critical issues like this from slipping through we are working on an automated test system. The headless version of x64dbg introduced in the previous release was a first step in this direction, but much more work is required. This release also introduced support for AddressSanitizer, which helps prevent memory safety issues.
❓ Documentation
The documentation has now been moved to the
docsfolder in the x64dbg repository. This streamlines development, but also makes the project much more LLM-friendly. Practically-speaking this means you can now ask questions about x64dbg in DeepWiki and expect reasonably-useful results!Some example questions:
Obviously this is no replacement for reading the documentation, but it might at least point you to some concepts to research!
🔎 Tracing
There have been quite a lot of updates to the trace recording feature over the past few months by @torusrxxx. For those not familiar, trace recording allows you to capture the registers and memory accesses for every step of the program. Think Time Travel Debugging, but on a much smaller scale. This feature can be helpful trying to understand the data flow or figuring out where a specific value first pops up when executing a function.
To start a trace recording, use Help -> Trace into... and then enable the Record trace checkbox:
You can see a reconstruction of the memory/stack (best effort, might be slow on larger traces):
This version introduces support to search for intermodular calls in the trace, which can be useful to understand where APIs get called. A blog post with more details will follow!
🤖 Scripting
❗ You might want to check out Analysis at Scale with x64dbg Automate, which introduces a Python library to automate x64dbg. There is also an MCP Server built on top of it, which allows LLMs to interact with x64dbg.
The builtin scripting feature has always been a bit lackluster, but the need for testing automation has pushed things forward. Improved command line handling was introduced by @peace-maker and you can now specify a script to execute on debuggee startup:
x64dbg {OPTIONS} [filename] -- [extra arguments] x64dbg OPTIONS: -workingDir Current working directory of new process. Defaults to current working directory if not specified. (optional) -pid Process ID to attach to. (optional) -tid Thread Identifier (TID) of the thread to resume after attaching (PLMDebug). (optional) -event Handle to an Event Object to signal (JIT). (optional) -c Command to execute Specifies the initial debugger command to run at start-up. (optional) -cf Specifies the path and name of a script file. This script file is executed immediately on startup. (optional) -p Alias for -pid. (optional) -a Alias for -pid. (optional) -e Alias for -event (optional) -help Show this message. (optional)The scripting system has been rewritten from scratch to execute all of the script commands on an event loop, which ensures everything executes in a deterministic order. A lot of bugs have been fixed too, which enables more complex scripting scenarios:
The script above sets a breakpoint on
RtlEnterCriticalSection. It uses a breakpoint command to execute theanalyzefunction in the script every time the breakpoint hits, and performs some logging. For testing we can use the headless command line tool with test executables and scripts to make sure everything works as expected.🐧 Cross Platform
Thanks to @eldarkg you can now build x64dbg in Wine with a custom CMake toolchain. Additionally the first iteration of the
cross-platformbranch has been merged. Slowly the GUI components will be ported to anx64dbg::widgetslibrary that can be reused for other projects.🤝 Community
x64dbg is a community-driven project, and this release would not have been possible without the incredible work of our contributors. A huge thank you to everyone who contributed code, reported bugs, and helped shape this release ❤️
We recently revamped the Discord community, which you can join below:
Other platforms are synchronized with the
#generalchannel:❤️ Sponsors
This project is also made possible by the generous support of sponsors. We would like to give a special shout out to the following sponsors:
Also many thanks to my active sponsors: @LabGuy94, @grant-h, @MorpheusH3x, @re-jevi, @adam-the, @verdeckt, @emesare, @daaximus, @stevemk14ebr, @as0ni, @sedrakpc, @Dan0xE, @Invoke-RE, @leandrofroes, @shu-tom, @buzzer-re, @expend20, @crudd, @clayne, @fr0zenbag, @dzzie
If you find x64dbg valuable in your work, please consider becoming a sponsor. Your support directly funds development and helps us continue to build the future of debugging. For companies we also offer custom services depending on the level of sponsorship, please reach out for more details!
📜 Changelog
Full commit history:
2025.06.30...2025.08.19This discussion was created from the release 2025.08.19.
Beta Was this translation helpful? Give feedback.
All reactions