x64_dbg VS WinHex

x64_dbg mentions (16)

• Too Many Fonts in Windows 10 Can Cause Slow Application Starts

  I have never heard anyone say anything good about the Visual Studio debugger before. Now, I'm not a Windows person but I'm not gonna argue for gdb or lldb here. RemedyBG and x64dbg are the two debuggers I've heard good things about though I've never used them because, again, not a Windows person. [1] https://remedybg.handmade.network/ [2] https://x64dbg.com/. - Source: Hacker News / 9 months ago

• Advice needed on disabling license checks on some old proprietary abandonware

  I'd help you out but because of circumstances I have no laptop with me. You need x86/x64 debugger to do this. This one for example Find a registration procedure and look for possible brenching to other parts of code in assembly. It's probably somewhere in the beginning. Exclude code validation and export new program version. Source: 11 months ago

• C/C++: Where is the address of a declared variable stores?

  One interesting thing you can do is download an app like https://x64dbg.com/ or cheat engine, which will let you see the memory. You can look at the process for something you’ve made and explore it. Log a memory address from your app then go find it in the tool and interpret the bytes as an integer. Find a string and see how that works. Find a pointer, read the address it’s pointing then go look at that address.... Source: about 1 year ago

• Is there a tool that can show you an EIP trace of a game?

  If you want to also do dynamic analysis (debugging) you can use https://x64dbg.com. Source: over 1 year ago

• How do I get opcode instructions from hexdump

  .exe is a complex format and not something you're going to extract raw instructions from using a hexdump. What you need is a "disassembler". For Windows I'd recommend x64dbg. Source: over 1 year ago

WinHex mentions (0)