In this particular program, doing buffer handling in this way does not affect the execution time significantly, and in some data sets, affects it negatively.
在这个程序中，以这种方式执行缓冲区处理并不会显著影响执行时间，而对于某些数据集，可能有消极影响。
This error occurs if a program passes an invalid pointer value or if the length of the buffer is too small.
如果程序传递了无效的指针值，或者如果缓冲区的长度太小会发生此错误。
Buffer overflows begin with something every program needs: a place to put bits.
缓冲区溢位开始于每个程序都需要的一些情况︰放置位元的空间。
The simplest usage is to have the SPE program take two Pointers: one for an input buffer and one for an output buffer.
最简单的用法是让SPE程序使用两个指针：一个用于输入缓冲区，另外一个用于输出缓冲区。
The SPE program reads in the input buffer, processes the data, and then writes it to the output buffer.
SPE程序从输入缓冲区中读取数据，然后对数据进行处理，再将结果写入输出缓冲区中。
If an attacker can cause a buffer to overflow, then the attacker can control other values in the program.
如果攻击者能够导致缓冲区溢出，那么它就能控制程序中的其他值。
The kernel ring buffer is also used for some events after the system is booted. These include certain program failures and hot-plug events.
在系统启动后，内核环缓冲区也可以用于一些事件，其中包括某些程序失败和热插拔事件。
The example program would benefit from such enhancements as keeping the buffers synchronized or checking if the complete buffer must be redrawn when contents are lost.
示例程序将受益于一些增强功能：如使缓冲区保持同步，或者检查当内容丢失时是否必须重新绘制整个缓冲区。
Likewise, when a buffer overflows, the excess data may trample on other meaningful data that the program might wish to access in the future.
同样地，当缓冲区溢位时，额外的资料会摧残程序将来可能要存取的其它有用的资料。
For instance, a program designed to exploit a buffer overflow is very likely to use some inline assembly for the target platform.
举例来说，设计利用缓存溢出的程序很可能会对目标平台使用内联汇编。
In the sample program, event data is always read with a buffer of 4k.
在示例程序中，总是用4k的缓冲区读取事件数据。
In the worst cases, a program may be overflowing a buffer and not showing any adverse side effects at all.
最坏的情况是︰程序可能正发生缓冲区溢位，但根本没有任何副作用的迹像。
The example program purposely does not synchronize buffers by remembering what wasn't drawn to the current buffer — letting you see multiple buffers at work more clearly.
示例程序通过记住什么东西没有绘制到当前缓冲区来有意不让缓冲区同步—以便让您更清楚地了解同时工作的多个缓冲区。
In the instance of a buffer overflow attack, an internal value in a program is overflowed to alter how the program runs.
在缓冲区溢出攻击的实例中，程序的内部值溢出，从而改变程序的运行方式。
You could even just use a single pointer and write data back into the buffer you got it from, although this might be a nuisance to program for on the other end.
您甚至只需要使用一个指针并将数据写回到读取数据所使用的缓冲区中即可，不过这对于另外一端的编程来说可能有些麻烦。
In a buffer overflow attack, the hacker takes advantage of specific type of computer program bug that involves the allocation of storage during program execution.
在缓冲溢出攻击中，黑客利用了程序执行期间存储分配中的特定计算机程序漏洞。
This puts all of the transferring logic into the MFC, and leaves your program free to do other computational tasks while the buffer waits for new data.
这会将所有传输逻辑全部放入 MFC 中，并让程序可以在缓冲区等待新数据的同时自由地执行其他计算任务。
Looking at the program, it is also easier for an attacker to figure out how to cause a buffer overflow with real inputs.
检视这个程序，攻击者更容易得出如何利用实际输入导致缓冲区溢位。
Any program that allows an external entity to input data is vulnerable to malicious activity, such as buffer overflows and embedded control characters.
任何允许外部实体来输入数据的程序都容易受到恶意的攻击，例如缓冲区溢出和嵌入式控制字符。
The output of each program is then pasted back into the buffer, replacing the original contents.
然后将每个程序的输出粘贴回缓冲区，替换原有的内容。
For example, a buffer overflow in a network server program that can be tickled by outside users may provide an attacker with a login on the machine.
例如，外部使用者可以利用的网路伺服器程序中的缓冲区溢位，可能使攻击者登入到机器。
Donors are committed to expanding the program to new areas made available by the recent revision of the buffer zone.
捐助机构承诺将该方案扩大到最近缓冲区修改后腾出的新区。
A common cracking technique is to find a buffer overflow in an suid root program, and then exploit the buffer overflow to snag an interactive shell.
常用的破坏技术是在suidroot程序中寻找缓冲区溢位，然后利用缓冲区溢位偷取交谈式shell。
The sample program does not check for EVENT_OVERFLOW since it specifies an INFO_LVL of 1 and USES the default buffer size of 4k.
示例程序并不检查EVENT_OVERFLOW，因为它指定info_lvl为1并使用默认缓冲区大小4k。
A buffer overflow in a program such as find is likely to be a risk to a great number of systems.
诸如find这样的程序中的缓冲区溢出可能会给大量的系统带来风险。
But as a result, the buffer is never released because it is always reachable by the program (unless the LeakyChecksum object is garbage collected).
但是结果是，缓冲区永远不会被释放，因为它对程序来说总是可及的(除非leakychecksum对象被垃圾收集了)。
If the program USES the resulting data anyway, an attacker will try to fill up the buffer so that when the data is truncated, the attacker will fill the buffer with what the attacker wanted.
如果程序无论如何还是使用了结果数据，那么攻击者会尝试填满缓冲区，以便在数据被截断时使用他希望的任何内容来填充缓冲区。
Fundamentally, any time your program reads or copies data into a buffer, it needs to check that there's enough space before making the copy.
从根本上讲，在程序将数据读入或复制到缓冲区中的任何时候，它需要在复制之前检查是否有足够的空间。
Fundamentally, all these approaches reduce the damage of a buffer overflow attack from a program-takeover attack into a denial-of-service attack.
从根本上讲，所有这些方法都能减轻从程序接管攻击到拒绝服务攻击的缓冲区溢出攻击所带来的破坏。
Depth texture corresponds to Z buffer contents that are rendered, it does not use the result from the fragment program.
深度纹理对应于Z缓冲区所渲染的内容，它并不使用片段程序所输出的结果。
应用推荐