When your program breaks at the specified memory allocation, you can look at the Call Stack window and other debugger information to determine the conditions under which the memory was allocated.
当程序在指定的内存分配处中断时，可以查看“调用堆栈”窗口和其他调试器信息以确定分配内存时的情况。
The debugger and debug information is available or present in all software components, however, not all users are aware of what the debug data consists of and how the data is stored.
调试器和调试信息可用于或存在于所有软件组件中，然而，并不是所有用户都了解调试数据的组成以及数据的存储方式。
The debugger USES these basic pieces of information for debugging purposes.
调试器使用这些基本信息片段来实现调试目的。
The debugging information stored within a binary helps a programmer or debugger locate problem areas in a program, and find the stack trace when an error happens in an application.
二进制文件中存储的调试信息可以帮助程序员或调试人员寻找程序中出问题的地方，并在应用程序出错时找到栈跟踪。
With these pain points in mind, we set about to create a new debugger feature where the right information was collected at the time the problem occurred.
明确了这些要点之后，我们有了一个新的调试器功能的构想：它需要能够在问题发生的时候就搜集到正确的信息。
This data object holds the information required for debugging, and it's sent to the debugger when the debug session starts.
这个数据对象持有调试所需的信息，并且在启动调试会话时发送给调试器。
It is difficult to get debuggers to display the information the way we want it to be displayed, but a product-specific debugger helps in customizing the data for analysis.
让调试器按照我们希望的方式显示信息是很困难的，但是特定于产品的调试器有助于定制分析数据。
While refreshing the browser page, you should see breakpoint information, such as that shown in Listing 8, scrolling in the GDB Debugger xterm.
在刷新浏览器页面的同时，您应该看到如清单8所示的断点信息，在GD b调试器xterm中滚动输出。
While refreshing the browser page, you should see breakpoint information, such as that shown in Listing 11, scrolling in the GDB Debugger xterm.
在刷新浏览器页面的同时，您应该看到如清单11所示的断点信息，在gdb调试工具xterm中滚动输出。
UNIX actually encourages you to explore and learn by providing tools, such as strace and the GDB Debugger, as well as a wealth of information in the man and info pages.
实际上，UNIX通过提供各种工具，如strace和gdb调试工具以及包含在相应的man和info页面中的大量的信息，鼓励您对系统进行研究和学习。
The -quiet option tells the GDB Debugger to display only its prompt and not all the other startup information that it typically displays.
quiet选项告诉gdb调试工具仅显示其提示符，而不要显示所有其他的启动信息。
The attach 4009 command starts debugging the currently running nweb server, and the GDB Debugger responds in kind by reading all the symbolic information about the process it can.
attach 4009命令启动对当前正在运行的nweb服务器的调试工作，并且gdb调试工具通过读取有关该进程的所有的符号信息来做出同样方式的响应。
The GDB Debugger is such a useful tool that a lot of information about it is available on the Internet.
gdb调试工具非常有用，Internet上提供了大量的有关该工具的可用信息。
Listing 8: Breakpoint information in the GDB Debugger xterm.
清单8：gdb调试器xterm中的断点信息。
For more information on how to work with Eclipse and the debugger, consult the Eclipse documentation.
要了解关于如何使用Eclipse和调试器的更多信息，请参阅eclipse文档。
This information is also used by popular debugger tools, such as GDB and WDB.
也可以将这些信息用于流行的调试工具，如gdb和wdb。
Even with the debugger and profiler, all you get is information about what might be causing a performance problem, not necessarily any helpful advice on what you should do to fix it.
即使使用调试器和profiler，您所获得的也只不过是一些简单的信息：什么可能导致了性能问题，以及有关应该如何修复这些问题的一些不太必要同时也不太有用的建议。
Apart from using Purify APIs in the debugger, you can also embed them from programs for checking errors and reporting extra information.
除了使用这个调试器中的Purifyapi外，您还可以将它们嵌入程序来校验错误和报告额外的信息。
This is not a debugger bug, but it is known issue with try catch block debug information. See the following disassembled code for an example of a try catch block in the debugger.
这并不是调试器的bug，但是这是针对trycatch块调试信息的一支问题。
To perform the debug of an application without a debugger by extracting the debug information separately and storing it in separate files.
在缺少调试器的情况下执行应用程序调试，方式是分别提取调试信息，并将它们存储到不同的文件中。
The debugger displays a lot of information, and it is grouped into different sections called views.
调试器显示了大量的信息，并且可以分组到不同的称为视图的部分中。
Using a debugger makes finding all of this information simple.
使用调试器将使找出所有这些信息变得很简单。
When the LocalCDILaunchDelegate is called upon to launch in debug mode, it obtains information about the executable to be debugged and the parameters to be sent to the debugger.
当调用LocalCDILaunchDelegate以在调试模式下启动时，它将获得有需要调试的可执行文件的信息以及将发送给调试器的参数。
Running a page in the debugger makes it possible for you to step through code line-by-line and use additional analysis tools and runtime information.
在调试器中运行页使您可以逐行通过代码，并利用其他分析工具和运行时信息。
For more information, see Changing the Numeric format of Debugger Windows.
有关更多信息，请参见更改调试器窗口的数值格式。
For more information about valid expressions, see expressions in the Debugger.
有关有效表达式的更多信息，请参见调试器中的表达式。
When you specify the -V option on the command line, the compiler appends Turbo Debugger 5.0-compatible external debug information at the end of the executable file.
当你在命令行中使用-V选项时，编译器会在可执行文件的末尾附加与Turbo Debugger5.0一致的外部调试信息。
The diagnostics symbol store API enables a compiler to generate symbol information for use by a debugger.
诊断符号存储区API可使编译器生成供调试器使用的符号信息。
When managed code generates an exception, the CLR debugging API suspends the execution of the process and passes the exception information to the debugger.
当托管代码生成异常时，clr调试api将暂停执行进程，并将异常信息传递给调试器。
When managed code generates an exception, the CLR debugging API suspends the execution of the process and passes the exception information to the debugger.
当托管代码生成异常时，clr调试api将暂停执行进程，并将异常信息传递给调试器。
应用推荐