You can use gdb to debug user-space programs or the Linux kernel.
您可以使用gdb来调试用户空间程序或Linux内核。
The GNU Debugger (gdb) is the most popular open source debugger in use.
GNUDebugger（gdb）是目前最受欢迎的开源调试器。
This is so gdb can work out the variables, lines and functions being used.
这样，gdb 才能够调试所使用的变量、代码行和函数。
The gdb uses the serial line to communicate to the kernel you are debugging.
gdb使用串行线与您要调试的内核通信。
This article explains how MI works and how the CDT uses MI to communicate with gdb.
本文解释了MI 的工作原理以及CDT如何使用 MI与gdb通信。
The resulting file, called gdb-ui.el, tries to use all of these features as well as those in gdba.el.
其成果gdb-ui.el尝试使用这些 新特性，以及gdba.el中的那些特性。
The next set of GDB definitions to incorporate into your.gdbinit file display useful process information when they're invoked, as shown in Listing 2.
要整合到.gdbinit文件中的下一组gdb定义将在进程被调用时显示有用的进程信息，如清单2所示。
To see what's going on in main() we can set a breakpoint at a particular line or on a function in the program code so gdb will interrupt execution when it is reached.
为了查看在main()中发生了什么情况，可以在程序代码中的某一特定行或函数中设置断点，这样gdb会在遇到断点时中断执行。
We had to continue program execution twice to get to this point, however by setting a condition on the breakpoint we can make gdb halt only when "value" actually equals "div".
我们必须继续执行两次程序才会发生这种情况，但是只要在断点上设置一个条件就可以使gdb只在 "value" 与 "div"真正相等时暂停。
Note: The -ggdb option in Listing 2 differs from Nigel's article in that it tells the GCC compiler to optimize the program for debugging with the GDB Debugger, which you'll use later.
注意：清单2 中的 -ggdb选项和Nigel的文章中的内容有些不同，该选项用于告诉GCC编译器对该程序进行优化，以便使用 GDB调试工具对其进行调试，您将在以后用到该调试工具。
Scenario 3: Using GDB and oops.
第3种情况：使用gdb和oops。
gdb是gnu调试器。
Your screen clears, and all you see is the GDB prompt.
此时屏幕被清除，您所看到的就只有gdb提示符。
Note, however, that this feature requires GDB 6.0 or later.
不过要注意的是，这个功能需要GDB 6.0或更高版本。
Listing 8: Breakpoint information in the GDB Debugger xterm.
清单8：gdb调试器xterm中的断点信息。
This tutorial has covered the most basic features of GDB-UI.
本教程涉及了GDB - UI的基本功能。
However, to debug, X86 assembly users need to resort to GDB.
尽管如此，为了调试X86汇编，用户需要依靠GDB。
Two important GDB Debugger commands are list and disassemble.
有两个重要的gdb调试工具命令，它们分别是list和disassemble。
It's a well-known fact that many of the GDB commands are too verbose.
许多GDB命令太繁琐，这是众所周知的事实。
Then, it starts GDB and creates two session objects to manage debug data.
然后，它启动gdb并创建两个会话对象来管理调试数据。
GDB is more standardized across different architectures and distributions.
gdb更为标准化，可跨不同体系结构和发行版本使用。
Hook-stop is a special definition that GDB calls at every breakpoint event.
hook - stop是GDB在每次发生断点事件时调用的特殊定义。
This information is also used by popular debugger tools, such as GDB and WDB.
也可以将这些信息用于流行的调试工具，如gdb和wdb。
When GDB responds, the process of updating the Signals View takes five steps.
当gdb响应后，更新Signals视图的过程需要五个步骤。
Now that we're finished debugging, GDB can be exited with the 'quit' command.
现在已完成了调试，可以使用'quit'命令退出gdb。
Meanwhile, the RxThread is constantly reading the InputStream from the GDB process.
同时，RxThread不断读取来自gdb进程的InputStream。
The KGDB utility is a debugger based on GDB that allows debugging of kernel core files.
kgdb实用程序是基于gdb的调试器，允许调试内核核心文件。
Listing 9 displays a GDB exception after the mount command to the file system is issued.
清单9在向文件系统发出mount命令之后显示一个gdb异常。
You can view extensive GDB online help and a detailed tutorial by using the help command.
您可以使用help命令查看全面的gdb在线帮助和详细的教程。
In many cases, the MI result record is followed by (GDB) and an out-of-band (OOB) record.
在许多情况下，MI结果记录之后是(gdb)和带外(out - of - band,OOB)记录。
应用推荐