3 ms·
I still struggle with GDB but my excuse is that I seldom use it. When I was studying reverse engineering though, I came across a really cool kit (which I've ye
by dijit 5y ago
I still struggle with GDB but my excuse is that I seldom use it.
When I was studying reverse engineering though, I came across a really cool kit (which I've yet to find an alternative for lldb, which would be nice given: rust)
I'd recommend checking it out, if for no other reason than it makes a lot of things really obvious (like watching what value lives in which register).
https://github.com/hugsy/gef https://github.com/hugsy/gef
LLDB's closest alternative to this is called Venom, but it's not the same at all. https://github.com/ovh/venom https://github.com/ovh/venom
- synergy20 5y agoI was using gdb-dashboard: https://github.com/cyrus-and/gdb-dashboard https://github.com/cyrus-and/gdb-dashboard seems kind of like gef.
- doix 5y agoIn a past life I used Voltron[0] with lldb. Depending on your use case, it might be enough? Watching what value lives in what register works at least (or at least worked last time I used it). It's designed around having things in separate terminals, so you'll need tmux/screen/tiling window manager to get a similar view to gef. [0] https://github.com/snare/voltron https://github.com/snare/voltron