![]() It has a layout positioned just above the command line where you can enter typical GDB commands. GEF shows most any information you'd need and has a very similar layout to what you'd see in a graphical binary debugger. GEF (pronounced 'Jeff') is a powerful, but still lightweight, configuration for GDB. I still recommend this configuration, as it's easy to install, and it's a great entry point for GDB customization. What I really liked about it was that it was lightweight and showed me most everything I needed to see after each step. I started using it then and really enjoyed it. This, or something very similar to it, used to be packaged in BackTrack Linux (the precursor to Kali Linux). They're GDBInit from OSXReverser, GEF, gdb-dashboard, and PwnDbg. Specifically, they're a few projects hosted on GitHub, and they've made GDB much faster for me to use, and I was pretty comfortable there, to begin with. So, I've been working on a few different projects over the past few months that make this a bit easier. And, you can't really tell where the valid pointer is, and ARRRRRRGGGH I JUST HIT 'N' NOT 'SI' SO I NEED TO START OVER. ![]() I mean, so you can see what's in EIP, it seems okay, but you need to trace a value at the end of some pointer chain staring in RAX. GDB is very powerful, but the commands can be difficult to keep in mind. ![]() If you're working in either IoT or cybersecurity, you're likely using GDB (and LLVM, WinDbg, and so on).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |