awesome-cpp VS x64dbg

Regardé: Awesome-CPP

Here's a list of (globally) well-written C++ libraries: https://github.com/fffaraz/awesome-cpp

Here is a list of free online C/C++ books: https://github.com/fffaraz/awesome-cpp/blob/master/books.md

If you need some library you can try searching thjs list https://github.com/fffaraz/awesome-cpp

Here's a big list of a bunch of high quality C++ libraries and codebases. Hopefully you can find something in your areas of interest and can dive into it.

Could you detail what exact tooling you are talking about ?

Like, this static analyzer looks interesting but 5 years ago clang --analyze had no trouble producing me a nice html indicating the 27 steps across 6 functions that lead to a pointer being dereferenced after being deleted. Tooling is there but it seems that pretty much no one is aware of it - see e.g. this: https://github.com/cpp-best-practices/cppbestpractices/blob/... or this: https://github.com/fffaraz/awesome-cpp for a quick look at what exists.

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/

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.

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. You start to see how different containers store data. I find it fascinating.

If you want to also do dynamic analysis (debugging) you can use https://x64dbg.com.

close origin and download this debugger https://github.com/x64dbg/x64dbg/releases

.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.

Patch the DayZServer_x64.exe, change "test al, al" to "cmp al, 2". i used x64dbg (https://x64dbg.com) a good video for the whole process: https://drive.google.com/file/d/1F1A0lpumREPXtVeoTMq1HiEnvaZp-NUU/view