I am using API Monitor v2 to debug and reverse engineer a 32bits application running on Windows 10 but I'm having some issues figuring out a std::set object values, I'm trying to dump the memory to a file so I can better look at the object with assistance of Hex Workshop structures.
While inside API Monitor's "Memory Editor" I can see the entire process memory and all pointers are valid but dumping the memory with ProcDump gives me an unaligned file, I tried padding, but it didn't work that well...
I've also tried github.com/glmcdona/Process-Dump but it creates one file for each .dll which is not useful for me in this situation where I have to navigate the memory... Is the solution using another tool? IDA seems overkill, Ollydbg feels counter intuitive, I could try Ghidra... Or maybe there is some technique to padding the mem dump?
Ps. The program has been frozen by API Monitor using a breakpoint, so this isn't the case of the memory simply changing.
In the end all I wanted to do was figure out what values where written in a
std::setvariable. I haven't really used a debugger before and having to learn how to do so for such a simple task felt wrong, I ended up writing a small Python script to extract the values stored in the set.You have to make sure that the memory dump section where the set resides has the same start address as it does in memory.