StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<h1>.gdbinit</h1> <p>You can tweak your <code>~/.gdbinit</code> to have colors. You can use mammon's <code>.gdbinit</code> which is available here:</p> <p><a href="https://github.com/gdbinit/gdbinit" rel="noreferrer">https://github.com/gdbinit/gdbinit</a></p> <p>You can tweak it as much as you want too. I found this thanks to <a href="https://stackoverflow.com/questions/5526432/gdb-in-backtrack">this SO answer</a>. Here's the kind of output that you can obtain:</p> <p><img src="https://i.stack.imgur.com/Nhuwf.png" alt=".gdbinit"></p> <p>A GitHub repository is also available: <a href="https://github.com/gdbinit/Gdbinit" rel="noreferrer">https://github.com/gdbinit/Gdbinit</a></p> <p>On a side note, the same idea was also <a href="https://github.com/deroko/lldbinit" rel="noreferrer">applied to lldb</a>.</p> <h1>GDB Dashboard</h1> <p>Following the same concept, <a href="https://github.com/cyrus-and/gdb-dashboard" rel="noreferrer">GDB Dashboard</a> provides a modular visual interface for GDB in Python.</p> <p><a href="https://i.stack.imgur.com/mHC8f.png" rel="noreferrer"><img src="https://i.stack.imgur.com/mHC8f.png" alt="GDB Dashboard"></a></p> <h1>(void)walker</h1> <p>Another similar project uses GDB's Python support to provide more extensibility, so this is worth checking out: <a href="https://github.com/dholm/voidwalker" rel="noreferrer">https://github.com/dholm/voidwalker</a></p> <p>@dholm also provides his own <a href="https://github.com/dholm/dotgdb" rel="noreferrer">.gdbinit</a> inspired from the previous one.</p> <p><img src="https://raw.githubusercontent.com/dholm/voidwalker/master/screenshot.png" alt="(void)walker"></p> <h1>pwndbg</h1> <p>Some projects provide a set of useful functions, including improved display. This is the case for <a href="https://github.com/longld/peda" rel="noreferrer">PEDA</a> or <a href="https://github.com/zachriggle/pwndbg" rel="noreferrer">pwndbg</a>. The latter gives the following description:</p> <blockquote> <p>A PEDA replacement. In the spirit of our good friend <code>windbg</code>, <code>pwndbg</code> is pronounced <code>pwnd-bag</code>.</p> <ul> <li>Speed</li> <li>Resiliency</li> <li>Clean code</li> </ul> </blockquote> <p>It provides commands to support debugging and exploit development similar to the ones from PEDA, and better display (although this is not the main focus of the project). The software is still under development, and has not been properly released yet.</p> <p><a href="https://i.stack.imgur.com/BuVHv.png" rel="noreferrer"><img src="https://i.stack.imgur.com/BuVHv.png" alt="pwndbg"></a></p> <h1>voltron</h1> <p>The <a href="https://github.com/snare/voltron" rel="noreferrer">project</a> description states:</p> <blockquote> <p>Voltron is an extensible debugger UI for hackers. It allows you to attach utility views running in other terminals to your debugger (LLDB or GDB), displaying helpful information such as disassembly, stack contents, register values, etc, while still giving you the same debugger CLI you're used to.</p> </blockquote> <p>You can modify your <code>.gdbinit</code> to automatically integrate it. However, the display itself is outside of GDB (e.g. in a tmux split).</p> <p><a href="https://i.stack.imgur.com/7eWF1.png" rel="noreferrer"><img src="https://i.stack.imgur.com/7eWF1.png" alt="voltron"></a></p> <h1>GEF</h1> <p><a href="https://github.com/hugsy/gef" rel="noreferrer">GEF</a> is another option, and it is described as:</p> <blockquote> <p>It is aimed to be used mostly by exploiters and reverse-engineers, to provide additional features to GDB using the Python API to assist during the process of dynamic analysis and exploit development.</p> </blockquote> <p><a href="https://i.stack.imgur.com/EpxEz.png" rel="noreferrer"><img src="https://i.stack.imgur.com/EpxEz.png" alt="GEF"></a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload