https://blog.qife122.com/tags/ddd/ Recent content in DDD on 办公AI智能小助手 Hugo zh-cn qife Mon, 08 Dec 2025 14:54:56 +0800 https://blog.qife122.com/p/%E4%BD%BF%E7%94%A8gdb%E5%92%8Cddd%E8%BD%BB%E6%9D%BE%E8%B0%83%E8%AF%95/ Mon, 08 Dec 2025 14:54:56 +0800 https://blog.qife122.com/p/%E4%BD%BF%E7%94%A8gdb%E5%92%8Cddd%E8%BD%BB%E6%9D%BE%E8%B0%83%E8%AF%95/ <h1 id="pleasant-debugging-with-gdb-and-ddd">Pleasant debugging with GDB and DDD</h1> <h2 id="gdb-front-ends">GDB front ends</h2> <p>By default, GDB provides a terse line-based terminal. You need to explicitly ask to print the source code being debugged, the values of variables, or the current list of breakpoints. There are four ways to customize this interface. Ordered from basic to complicated, they are:</p> <ol> <li>Get used to the default behavior. Then you’ll be comfortable on any system with GDB installed. However, this approach does forego some real conveniences.</li> <li>Enable the built-in GDB TUI mode with the <code>-tui</code> command line flag (available since GDB version 7.5). The TUI creates Curses windows for source, registers, commands, etc. It’s easier to trace execution through the code and spot breakpoints than in the default interface.</li> <li>Customize the UI using scripting, sourced from your <code>.gdbinit</code>. Some good examples are projects like <a href="https://github.com/cyrus-and/gdb-dashboard">gdb-dashboard</a> and <a href="https://github.com/hugsy/gef">gef</a>.</li> <li>Use a graphical front-end that communicates with an “inferior” GDB instance. Front ends either use the GDB machine interface (MI) to communicate, or they screen scrape sessions directly.</li> </ol> <p>In my experiments, the TUI mode (option two) seemed promising, but it has some limitations:</p>