例如，如果对字节码故意做了更改，或者在通过网络传送类文件时现出了错误，那么就可能发生这个异常。
This could occur if the bytecodes had been deliberately hacked, for example, or if an error had occurred when transferring the class file over a network.
仔细查看，就会发现硬盘事实上在扇区之间包括大量额外数据，这些额外字节由磁盘固件使用，以检测和纠正每个扇区内的错误。
When you look closer, hard disks actually include a great deal of extra data in between sectors. These extra bytes are used by the disk's firmware to detect and correct errors within each sector.
由于第一个字符是多字节的，因此会导致字符分解和错误输出。
Since the first character is multi-byte, it results in splitting the character and leads to dirty output.
read函数返回读取的字节数（最高为您指定的最大值）；或者 -1，表示错误；或者0，如果已经到达文件末尾。
The read function returns the number of bytes read (up to the maximum that you specify), -1 on error, or zero if the end of the file has been reached.
例如，假设一个程序会错误地覆盖malloc已经分配的字节。
For example, let's assume that there is a program which incorrectly overwrites the number of bytes it has been allocated by malloc.
我常愿意在开始的几个字节后面启动模糊测试，因为程序似乎更可能注意到早期的错误而不是后面的错误。
I usually like to start fuzzing somewhere after the first few bytes because programs seem more likely to notice an early mistake than a later one.
前 446个字节是主引导加载程序，其中包含可执行代码和错误消息文本。
The first 446 bytes are the primary boot loader, which contains both executable code and error message text.
平均吞吐量的统计信息和复制的字节印总量被打印到标准错误输出设备。
Statistics of average throughput and the total amount of bytes copied are printed to the standard error output.
除非碰到EOF或出现错误，否则read应该返回所请求的字节数的数据；否则，其余数据都会被替换成0。
Read should return exactly the number of bytes requested, except on EOF or error; otherwise, the rest of the data will be substituted with zeroes.
模拟阅读开始于addr的size字节，产生读取将会导致的任何purify错误，根据错误调用purify_stop_here。
Simulates reading size bytes starting at address addr, generates any purify errors that read would cause, and calls purify_stop_here upon error.
模拟写入开始于addr 的size字节，产生写入将会导致的任何Purify错误，根据错误调用 purify_stop_here。
Simulates writing size bytes starting at address addr, generates any Purify errors that write would cause, and calls purify_stop_here upon error.
除非碰到EOF或出现错误，否则write应该返回所请求的字节数的数据。
Write should return exactly the number of bytes requested except on error.
换句话说，校验字节的监测和检测过的SONET帧的不同部分中的错误。
In other words, parity bytes monitor and detect errors over different parts of a SONET frame.
res是IO操作的通常结果：传输的字节数，或者负值的错误码。
res is the usual result of an I/O operation: the number of bytes transfered, or a negative error code.
造成这个错误的原因是，变化的长度占用2字节，null 占用 1 字节。
The error is caused by the fact that there is an overhead of two bytes for varying length and a one-byte overhead for null.
设定块的的长度小于512字节将会导致写入错误。
A set block length of less than 512 bytes will cause a write error.
更重要的是，每一层都使用一个单一的，交错的校验字节提供一个特定的市场上的错误监测以及终端到终端的SONET路径。
Importantly, each layer USES a single, interleaved parity byte to provide error monitoring across a particular segment, along the end-to-end SONET path.
符合BellcoreGR- 253SONET网络标准定义了一个特定的奇偶校验错误计算的字节。
The Bellcore GR-253 standard for SONET networks defines the bytes over which a particular parity error is calculated.
这个函数返回成功读取的字节数；如果发生错误，那么函数将返回False。
This function returns the number of bytes read on success, or FALSE and an error on failure.
此警告指出函数调用的参数可能是字节数，而不是字符数。这是错误的。
This warning indicates that a parameter to a function call might incorrectly be a byte count instead of a character count.
一个字节通常有8位，代表一个字符，而第9位是用来检验错误的。
A byte commonly contains 8 bits to represent a single character, and the ninth bit is used for error detection.
一个代表修补属性字节标志。值1表示应用此修补失败不是一个严重错误。
A bit flag representing patch attributes. A value of 1 indicates that the failure to apply this patch is not a fatal error.
你是怎么创建这些类？你做任何字节码操作吗？如果是这样，你可能有一个错误在您的代码中。
How did you create these classes? Did you do any bytecode manipulation? If so, you probably have a bug in your code.
你是怎么创建这些类？你做任何字节码操作吗？如果是这样，你可能有一个错误在您的代码中。
How did you create these classes? Did you do any bytecode manipulation? If so, you probably have a bug in your code.
应用推荐