When satisfied with the debug results, the developer can move the COBOL code back to a mainframe PDS for integrated testing and the move to production.
对调试结果满意时，开发人员可以将COBOL代码移回一个大型机pds进行集成测试，然后将其移到生产中。
Every developer deserves a fantastic development environment that allows them to write, understand, navigate, and debug code as efficiently as possible.
每个开发人员都值得拥有一个美妙的开发环境。这个环境可以让他们尽可能高效地编写、理解、浏览和调试代码。
With this debug code, we'll see what is selected and learn a little more about what makes Eclipse work.
有了这个调试代码，我们将看到选择了什么，并了解到有关什么使Eclipse工作的更多信息。
Use this code snippet to create a button the user can press to write "Hello World!" to the debug window.
使用此代码片段创建一个按钮，用户可以按下该按钮将“Hello World ！”写入调试窗口。
The following are absolutely essential in trying to locate and fix a bug: analyzing your code, attaching to running processes that you want to debug, and changing code and variables at runtime.
要找到程序中的bug，以下步骤是不可缺少的：分析代码，连接你要调试的运行中的进程，然后在运行时修改代码与变量。
After you compile the code with GCC -g -o0 simple.c -o simple, a regular debug session might look like Listing 2.
用gcc- g - O0simple . c -o simple编译代码后，一个常规的调试会话如清单2所示。
The Variables view in Figure 20 provides a live list of variables defined by the code as the debug session progresses.
在调试会话的过程中，图20中的Variables视图会提供代码定义的变量的列表。
It is a great way to test and debug your code directly on the server.
它是直接在服务器上测试和调试代码的一种最佳方式。
Adding debug statements to your code to write out the fields in an object, or even entire data collections, is a common problem-solving approach.
通过在代码中添加调试语句来输出对象的域或者甚至于整个数据集合是一种常用的解决问题的方法。
You can edit source code files, compile and debug your project seamlessly from within a single IDE.
在单个ide中，您可以无缝地编辑源代码文件、编译和调试您的项目。
This very simple application could be easily extended to become a very sophisticated and complex one, though the process to code, test and debug it would be similar.
您可以很容易地将这个非常简单的应用程序扩展为一个非常复杂的应用程序，但它们的编码、测试和调试的过程却是相似的。
Originally designed for C, it's been ported to debug code in many languages on a variety of computing systems, from tiny embedded devices to large-scale supercomputers.
它最初是为C 语言设计的，后来被移植到各种计算系统（从小型嵌入式设备到大型超级计算机）中调试多种语言的代码。
When you inherit new code, a quick scan can reveal issues that would take much longer to debug later on.
继承新代码时，快速扫描可以发现各种问题，从而避免稍后花费更多时间进行调试。
Before generating the code for production, it's a good idea to debug the EGL code.
在生成用于生产的代码之前，调试EGL代码是个不错的主意。
To debug the code you have to set a breakpoint first.
要调试代码必须先设置断点。
It's much easier to include the code to check for the exception than to try to debug a crash later on.
添加异常检测代码要比在事后尝试调试崩溃简单很多。
As inexperienced programmers start to built bigger applications, most of the time, the code becomes so unstructured that it becomes very hard to debug or modify even a small change.
随着程序员新手开始编写大些的应用时，多数情况下，他们编写的代码会变得毫无组织条理，以至在Debug或是做出小变动时，他们会犯难。
Because there is a memory leak in the application, Barb knows that she will have to debug the code and deploy a patch to the application running in production.
因为该应用程序中存在内存泄漏，所以Barb知道她将必须对代码进行调试，并为产品中运行的应用程序部署一个修补程序。
The most powerful tool for servicing Eclipse plug-in code is the Eclipse debugger's ability to debug a customer's workbench, even when that customer's workbench is running on a remote machine.
用于维修Eclipse插件代码的功能最强大的工具是 Eclipse调试器调试客户工作台的能力，即便客户的工作台运行于远程机器上也不例外。
As a rule, code compiled with full optimization can be difficult or impossible to debug, making it very difficult to identify bugs that may be causing the system to function incorrectly.
通常，经过完全优化的编译代码很难或者几乎不可能进行调试，这就加大了发现那些造成系统功能错误所在的难度。
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块调试信息的一支问题。
In the Disassembly window, click on a line of code and choose Toggle Breakpoint from the Debug menu.
在“反汇编”窗口中，单击代码行，然后从“调试”菜单中选择“切换断点”。
Another possible cause is trying to debug a dump file for managed code.
另一可能原因是：尝试调试托管代码的转储文件。
This isn't a huge issue, but it does mean that we won't have the ability to easily debug all the library code during development.
这不是一个大问题，但它确实意味着，我们将不会有能力在开发过程中轻松地调试所有的库代码。
When you run a debug build, those modules are considered to be user code.
运行调试版本时，将这些模块视为用户代码。
Debug your mixed code as a 32-bit process, as described in the following procedures.
作为32位进程调试混合代码，如下面的过程所述。
This code runs perfectly in a debug version of an MFC application.
此代码在MFC应用程序的调试版本中运行良好。
This code runs perfectly in a debug version of an MFC application.
此代码在MFC应用程序的调试版本中运行良好。
应用推荐