x64dbg | source user mode debugger for Windows | Code Inspection library

 by   x64dbg C++ Version: snapshot License: Non-SPDX

kandi X-RAY | x64dbg Summary

kandi X-RAY | x64dbg Summary

x64dbg is a C++ library typically used in Code Quality, Code Inspection applications. x64dbg has no bugs, it has no vulnerabilities and it has medium support. However x64dbg has a Non-SPDX License. You can download it from GitHub.

An open-source binary debugger for Windows, aimed at malware analysis and reverse engineering of executables you do not have the source code for. There are many features available and a comprehensive plugin system to add your own. You can find more information on the blog!.

            kandi-support Support

              x64dbg has a medium active ecosystem.
              It has 40922 star(s) with 2161 fork(s). There are 2766 watchers for this library.
              It had no major release in the last 12 months.
              There are 538 open issues and 1751 have been closed. On average issues are closed in 99 days. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of x64dbg is snapshot

            kandi-Quality Quality

              x64dbg has 0 bugs and 0 code smells.

            kandi-Security Security

              x64dbg has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              x64dbg code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              x64dbg has a Non-SPDX License.
              Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

            kandi-Reuse Reuse

              x64dbg releases are available to install and integrate.
              Installation instructions are available. Examples and code snippets are not available.
              It has 78 lines of code, 0 functions and 2 files.
              It has low code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of x64dbg
            Get all kandi verified functions for this library.

            x64dbg Key Features

            No Key Features are available at this moment for x64dbg.

            x64dbg Examples and Code Snippets

            No Code Snippets are available at this moment for x64dbg.

            Community Discussions


            What is this "r8d" in x64dbg?
            Asked 2021-Nov-21 at 03:46

            I'm debugging my x64 c++ program to learn how it look in x64dbg. I see some register for r8-r15 on the right window, but I don't see r8d. There were others like r15d too. So what is it?

            Here is a screenshot of my x64dbg.



            Answered 2021-Nov-21 at 03:46

            The d suffix means its (the 64-bit register's) lower double-word. For example, r8d is accessing r8's lower 32-bit as if it is a 32-bit register.

            You can find more info here.

            Source https://stackoverflow.com/questions/70051401


            What is the exact difference and the relation between thread entry and thread start?
            Asked 2021-Jan-28 at 10:14
            1. What is the exact difference between thread entry and thread start ? and
            2. does RIP (where the execution front is, in a dynamic analysis) always reaches them in the same predictable order ?
            3. is thread entry changing dynamically (in dynamic analysis I think I saw it being reported in registers and stack) ?

            I understand so far that thread start is defined from a point of view, eg., in Windows, it's always ntdll.RtlUserThreadStart+21 (User) but at the program library level, it can be any function. But the thread start is not called before the thread is created ntdll.NtCreateThreadEx+14 (System).

            The thread entry is the (library ie., exported, or private) function given as argument to the thread create function.

            An example of a callstack with threads (threadID, Address, to, from, size, comment, party) made with x64dbg:



            Answered 2021-Jan-27 at 21:14
            1. The terms in question do not necessarily have precise definitions in common jargon. The x64dbg docs you linked give these definitions:
            Thread Entry

            Set a single-shoot breakpoint on the entry of the thread when a thread is about to run.


            Thread Start

            Pause when a new thread is about to run.

            These are that debugger's chosen labels for what are apparently different kinds of events to which it can alert you. My interpretation, which is consistent with what you describe in the question, is that "thread start" is about the creation of a new thread, apparently in the context of the thread that does the creating, whereas "thread entry" is about execution of the code that will run in the new thread, presumably in the context of that thread.

            1. I would be inclined to think that, in these terms, thread start must always happen before thread entry. Execution cannot enter the code of a thread before that thread has started. Indeed, I would be inclined to guess that a thread start event is the very last one the debugger can signal that definitely comes before thread entry for the thread in question.

            2. In a general sense, I would expect a thread entry address to be the address of the thread's entry point function, or perhaps of the first instruction in its body (not necessarily the same thing). This cannot be expected to be consistent for different entry-point functions, and it might not be the same for the same function on different runs of the program. If you think you see something else then consult the tool's documentation.

            Source https://stackoverflow.com/questions/65926429


            How to break in x64dbg from ghidra's corresponding instructions?
            Asked 2021-Jan-26 at 14:22

            I have x64dbg and ghidra synchronized via ret-sync. I found an interesting point in ghidra:



            Answered 2021-Jan-19 at 09:06

            You said you wanted to go to 328b4 but your second snippet is at ...32B4 and looks like you ended up in the middle of an instruction. I would expect the correct address to be 0x00007FF8B2F81000 + 0x328b4 = 0x7ff8b2fb38b4.

            I am not aware of ret-sync supporting setting breakpoints, but you can do the address translation more easily by either getting the relative offset by hovering

            Source: https://twitter.com/dev747368/status/1347360276476293125

            and then adding the x64dbg offset of 00007FF8B2F81000 to offset (2008h in the screenshot, in your case 328b4h )

            Or you can script this by running currentAddress.subtract(currentProgram.imageBase) in the shell to get the relative offset for the current address (again 328b4h in your example) and then adding the x64dbg offset. So the complete command would be: currentAddress.subtract(currentProgram.imageBase).add(0x00007FF8B2F81000) Run this in the Python REPL and the correct x64dbg address for the current address should result.

            Source https://stackoverflow.com/questions/65768385


            Access method's parameter with dll injection
            Asked 2020-Nov-26 at 16:39

            I have a 64bit process, I figured out one of its statically linked library methods.

            Source of this method:



            Answered 2020-Nov-26 at 16:39

            If you can find out the address of the SSL_connect function you can detour it. This means that you can write a JMP instruction at the begin of the method to your patched-method.

            If your jumped-to method has the same calling convention and signature you can simply access SSL* and do what you want with it afterwards you can jump back...

            To let the jump back work you would need to restore the org code or create a copy of the org method...

            Another way would be a Hardware-Break-Point: read for example here.

            Source https://stackoverflow.com/questions/65025585


            x64dbg Windows APIs Stack details
            Asked 2020-Aug-13 at 21:15

            as I'm diving into the reverse engineering topic, I was wondering: is there any way (if possible) to have the same level of details, regarding Windows APIs Stack setup and arguments (highlighted in the Immunity image) within x64dbg?





            Answered 2020-Aug-13 at 21:15

            You may try xAnalyzer, you can download it here: https://github.com/ThunderCls/xAnalyzer

            Example output after applying this plugin:

            Source https://stackoverflow.com/questions/63377777

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install x64dbg

            You can also compile x64dbg yourself with a few easy steps!.
            Download a snapshot from GitHub, SourceForge or OSDN and extract it in a location your user has write access to.
            Optionally use x96dbg.exe to register a shell extension and add shortcuts to your desktop.
            You can now run x32\x32dbg.exe if you want to debug a 32-bit executable or x64\x64dbg.exe to debug a 64-bit executable! If you are unsure you can always run x96dbg.exe and chose your architecture there.


            This is a community effort and we accept pull requests! See the CONTRIBUTING document for more information. If you have any questions you can always contact us or open an issue. You can take a look at the easy issues to get started.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries

            Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular Code Inspection Libraries

            Try Top Libraries by x64dbg


            by x64dbgC++


            by x64dbgC


            by x64dbgPython


            by x64dbgPython


            by x64dbgC++