我不敢肯定这个目标是否能够实现，但我敢打赌您可以消除大多数程序中90%的错误消息，最终会得到一个更便于使用的系统。
I'm not sure whether that goal is possible, but I'll bet you could eliminate 90% of the error messages from most programs, and end up with a more usable system as a consequence.
无论使用什么系统，无论在将应用程序部署到生产环境中时进行什么样的功能和回归测试，您仍然会碰到一些无法避免的错误。
Regardless of what system you use and what functional and regression testing you do when your application is deployed for production, you can still get errors that are unavoidable.
如果应用程序找到了最后的可能项，而这一项是错误的，就需要让系统知道用户想的究竟是什么。
If the application gets to the last possible item and that item is wrong, you'll want to teach the system about whatever item the user really did think about.
当一个程序出错的时候，有很多进程是要在系统后台运行的（为了处理这个错误）。
There are many things that go on "under the hood" when program errors occur.
结果在象PalmOS或者Windows 95、98和ME这样的操作系统中，经常可能通过利用单个程序中的错误来更改其它程序中的数据。
The upshot of this fact is that in an operating system like the PalmOS, or Windows 95, 98 and ME, it is often possible to change data in other programs by exploiting a bug in a single program.
我还提供了名为showsyserr的小实用程序(请参阅参考资料)，它允许您查看系统错误消息。
I've also provided a small utility called showsyserr (see Resources), which allows you to see the system error messages.
系统内核所使用的内存空间通过特权码（privileged code，2级或者更低）来标记，以防止用户模式的程序访问到内核空间而发生页面错误。
Kernel space is flagged in the page tables as exclusive to privileged code (ring 2 or lower), hence a page fault is triggered if user-mode programs try to touch it.
如果错误是在JCL中，那么与管理员或者系统程序员联系以得到正确的信息。
If the error was in the JCL, contact your administrator or systems programmer to get the correct information.
实际上这在大部分产品系统中都不应该出现，但是在测试脚本位置发生变化或程序员输入了错误的URL 时，这种情况并不罕见。
This really shouldn't happen much in production systems, but it's not uncommon in testing for a script to move or for a programmer to enter an incorrect URL.
更换了手机，或只是安装了一些错误的应用程序时，可以要求进行系统恢复。
Having a phone swapped out, or just installing the wrong combination of apps could call for a system restore.
类型检查器应该能帮助程序员从这些类型的错误中恢复，但对于静态字段而言，类型系统实际上会使程序员更迷惑。
The type checker is supposed to help a programmer recover from exactly these sorts of mistakes, but in the case of static fields, the type system could actually help to confuse the programmer.
本最佳实践列表应该使架构师、系统管理员和应用程序开发人员能够避免常见的错误，并在他们的解决方案中最优地利用MQ。
This list of best practices should enable architects, system administrators, and application developers to avoid common mistakes and make optimal use of MQ in their solutions.
错误配置：当你手上有20中不同的智能设备，以及5个版本的操作系统，每个设备上运行着25个应用程序时会发生什么？
Misconfiguration: What happens when you get 20 different device types with 5 different versions of operating systems, and 25 different apps (that you care about) running on each?
他们一定使用了某种欺骗软件，一整套在全系统范围内耦合他们的错误的程序。
They must use deception software, some suite of programs that synchronizes their falsehoods system-wide.
它与保证应用程序不传递错误或者无意义的输入给CRM系统同样重要。
It's equally important to be sure that your application doesn't pass wrong or meaningless input to the CRM system.
事务属性和边界——各种错误各具特色，例如系统出错与程序出错，这种错误的特性影响不同的运行时平台如何处理自动回滚。
Transaction attributes and boundaries - Nature of errors such as system Vs application errors influences how different runtime platforms handle automatic rollbacks.
在那种情况下，即使您在一个自动测试系统中运行您的净化程序，当一个错误发生时，它将额外的消息转储到Purify日志中，那将帮助您鉴定这个问题。
In that case, even if you run your purified program through an automated test suite; when an error occurs, it will dump extra messages into the Purify log that will help you identify the problem.
实际上您可以使用系统中的strcmp，但是测试程序错误地认为缺少这个函数。
In fact, you could indeed use STRCMP on that system, but the test program incorrectly thought it was missing.
在设计良好的系统中，异常是程序错误处理的一部分。
In well-designed systems, exceptions represent a subset of the program's error handling.
管理员可能犯的最严重错误就是把服务器的所有资源如操作系统、第三方应用程序、页面空间以及应用程序数据等均置于单个卷组中。
The worst mistake an administrator can make is to put all of a server's resources—operating system, third-party applications, paging space, and application data—within a single volume group.
在第 2种情况中，我们使用了Linux 中的strace实用程序，它能够跟踪系统调用和信号，从而找出程序发生错误的地方。
Scenario 2 uses the strace utility in Linux that enables the tracing of system calls and signals to identify where a program is failing.
为每个系统调用计算次数、调用和错误，在程序退出时报告结果。
Count time, calls, and errors for each system call and report a summary on program exit.
用于解决软件和设备驱动程序错误时使用某些操作系统。
Used to troubleshoot software and device driver errors when using certain operating systems.
系统运行良好，能够针对高级语言初学者程序中出现的大部分错误，经过推理分析，指示并提出改正方法。
The system run well and can direct the most of errors for beginner of high programming languages and give the methods of correction thought reasoning and analysis.
然后运行程序，看系统是否提示错误，再顺藤摸瓜去解决。
Run a program next, see a system whether hint mistake, again track down by following clues goes solving.
我们在IBM - PC机上开发成功的程序语法错误诊断系统，就是以PAWDK知识库系统为主体的专家系统。
We have built a program syntactic errors debug system on IBM-PC computer. It is an expert system dependent on PAWDK knowledge base system.
我们在IBM - PC机上开发成功的程序语法错误诊断系统，就是以PAWDK知识库系统为主体的专家系统。
We have built a program syntactic errors debug system on IBM-PC computer. It is an expert system dependent on PAWDK knowledge base system.
应用推荐