Using them along with the debugger helps you track memory use with the program execution which manifests a memory error.
利用它们和这个调试器将帮助您跟踪带有程序执行的内存，这表明一个内存错误。
The simulator in essence is a debugger, so you can also set breakpoints and interact with the devices, CPU, and memory.
仿真器在本质上是调试器，因此您还可以设置断点并与设备、CPU以及内存进行互动。
This makes it easier for a debugger to identify which compilation unit created the code at a particular memory address.
这使得调试器可以更容易地确定哪一个编译单元在某个特定内存地址创建了代码。
Notice that you're telling the GDB Debugger to quit debugging a program that is still active in memory.
请注意，您正告诉gdb调试工具停止对一个仍在内存中活动的程序的调试。
It may use too much memory if you compile and run the GNU debugger, probably because it tends to open a window whenever you step into a program call.
如果您编译运行gnu调试器，可能会使用太多内存，或许是因为您进入一个程序呼叫时，它都试图打开一个窗口。
Internally, a debugger has direct access to the same memory space as the running process, while an external debugger will access the memory via a socket.
内部调试器对运行进程所在的内存空间具有直接访问权，而外部调试器将通过套接字访问内存。
IDLE's debugger provides breakpoints, stepping and variable watches; but nothing so fancy as poking at memory locations and variable contents, or performing timings and other analyses.
IDLE的调试器支持设置断点、单步执行和观察变量；但是不能获得内存位置和变量的内容，也不能进行执行的计时和其他统计。
For Scenario 1, we use two sample programs with memory allocation problems that we debug using the MEMWATCH and Yet Another Malloc Debugger (YAMD) tools.
在第1种情况中，我们使用了两个有内存分配问题的样本程序，使用MEMWATCH和YetAnotherMallocDebugger (YAMD)工具来调试它们。
When you are inside a debugger, you can use various Purify API functions to investigate the status and type of various memory locations.
当您在一个调试器中，您可以利用各种Purifyapi函数来研究各种内存单元的状态类型：f。
Purify offers a wide set of memory watch point APIs that you can call from the debugger to assist you in debugging the memory corruption problems in your program.
Purify提供了您可以从调试器中调用的范围较大的内存观察点集合，从而帮您在您的程序中调试内存泄露问题。
The Linux kernel debugger (KDB) is a patch for the Linux kernel and provides a means of examining kernel memory and data structures while the system is operational.
Linux内核调试器(Linux kernel debugger,kdb)是Linux内核的补丁，它提供了一种在系统能运行时对内核内存和数据结构进行检查的办法。
That allows you to examine and analyze relevant variables and memory contents in a debugger.
这样就允许您检查和分析相关的变量和调试器中内存的状态。
Memory analysis using a debugger is similar in either case, but the memory is accessed in different ways.
使用调试器进行内存分析类似于任何一种情况，但是使用了不同的方法访问内存。
A debugger potentially launches and attaches to a process to control it and to inspect its memory.
调试器可能启动并连接到进程上以便控制进程并监测其内存。
You might do this with a fault injection engine or a debugger, or maybe just by poking a value into memory by hand.
要达到这个目的，你可以使用错误注射引擎（Fault Injection Engine）或者调试器（debugger），甚至可能仅仅只需要手动把一个值写到相关内存区就行。
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.
当程序在指定的内存分配处中断时，可以查看“调用堆栈”窗口和其他调试器信息以确定分配内存时的情况。
You can easily copy the memory address of the desired function, paste it into your debugger, and set a breakpoint for this memory address.
您可以轻松地复制所需要的功能的内存地址，粘贴到您的调试器，并为这个内存地址断点。
The debugger client must implement this interface as appropriate for the particular target (for example, a live process or a memory dump).
调试器客户端必须根据特定的目标(例如，实时进程或内存转储)实现此接口。
The debugger client must implement this interface as appropriate for the particular target (for example, a live process or a memory dump).
调试器客户端必须根据特定的目标(例如，实时进程或内存转储)实现此接口。
应用推荐