4 ms·
In terms of simply poking around with memory cheatengine's UI is much more direct than (say) GDB or similar
by mhh__ 7y ago
In terms of simply poking around with memory cheatengine's UI is much more direct than (say) GDB or similar
- arsome 7y agoYeah, you could consider going to something like x64dbg for this case, but really for finding data in memory, CheatEngine is king.
- scottmcf 7y agoIt really says a lot that kids are so easily able to use/understand what is going on with Cheat Engine, despite how powerful it is.
- TeMPOraL 7y agoTells you that people with a goal to accomplish don't need to have their tools dumbed down for them, despite what modern UX trends would have you believe.
- userbinator 7y agoGDB is an absolute nightmare to use with Asm, it's almost like it was designed to discourage it. Look up the absolutely perplexing behaviour of the "disassemble" command[1] for one example --- the first time I encountered it, I exclaimed "WTF!?" out loud. WinDbg, and DOS's DEBUG that came before it, feel far more natural with such (and the former can also debug at source-level.) [1] "No function contains specified address." -- when there is absolutely no requirement for anything to resemble a function in order to be capable of being disassembled.
- saagarjha 7y agoHit a breakpoint? My fingers are already typing x/10i. LLDB does stupid things otherwise as well (I think it will automatically "move your cursor down"?) so this is just the command I always reach for.
- simias 6y agoYeah by default gdb sucks a bit for assembly, fortunately it's easily scriptable so I have a file with a bunch of functions to make it behave a bit more reasonably.