4 ms·
I would've put the binary into Ghidra, found the asm by EIP/RIP when the author found the segfault breakpoint in gdb or whatever, then looked for XREFs. That pr
by MuffinFlavored 4y ago
I would've put the binary into Ghidra, found the asm by EIP/RIP when the author found the segfault breakpoint in gdb or whatever, then looked for XREFs. That probably would've helped find where the memory/variable/code was. I'm not 100% sure that could've been traced back release -> debug build?
I take it the author didn't know this method, or... I might be missing something as to why that wasn't done?
- meibo 4y agoComing from a reverse engineering background and then going into regular sweng, I find myself wanting to grab IDA/x64dbg instead of my IDE's debugger very often... Sadly workplace politics prevent me from doing that and somehow everyone else is productive enough, so I'm just slowly getting used to living in Visual Studio.
- deleted 4y ago[deleted]
- MuffinFlavored 4y agowhat does it say about me that I go for printf()/println!()/console.log before an actual debugger? does it reveal that I'm basically a giant noob? lol
- saagarjha 4y agoNothing! Use the tools you have available to you, and pick whichever ones you're productive in. The only thing you should really look into is figuring out what each tool can offer you and being familiar with them, and then making an informed decision when you reach for a tool.
- saagarjha 4y agoThere's a large overlap between experienced debuggers and reverse engineers, because the tracing of a broken program is really a reverse engineering problem in disguise.