HxD VS x64_dbg

How does it compare to HxD? https://mh-nexus.de/en/hxd/. - Source: Hacker News / 2 months ago

By the sound of what happened it's possible that all files residing in the last 1TB got TRIMMed (https://www.300dollardatarecovery.com/trim/) by first aid. Can you check the corrupted videos with a hex editor (for example https://mh-nexus.de/en/hxd/) to see if they contain any information at all? If they got trimmed there will be large swathes of either 0xff or 0x00. Source: 5 months ago

You don't need to know anything about Hex-Editing to use this. You are only required to know how to copy-paste. That being said, you will need a Hex-Editor program and to know your save-file's location. I personally use HxD: https://mh-nexus.de/en/hxd/. Source: 11 months ago

Also, notepad is only good for editing text, not binary files. You should use a hex editor. I personally use HxD. I also found this online hex editor called HexEd.it. Source: 11 months ago

Anyway, due to the sheer size of the saves, I'd recommend using a hex editor like HxD rather than a text editor. Hex editors typically operate on just a small buffer at any given time, so opening and paging through the file is very fast. In theory, this might slow down full-file operations like a full text search, but in practice it doesn't seem to matter in this case. I opened a 100MB save that hasn't been... Source: 11 months ago

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

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

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

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

.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