IP : 18.227.48.208Hostname : host45.registrar-servers.comKernel : Linux host45.registrar-servers.com 4.18.0-513.18.1.lve.2.el8.x86_64 #1 SMP Sat Mar 30 15:36:11 UTC 2024 x86_64Disable Function : None :) OS : Linux
PATH:
/
home/
../
../
lib64/
libbz2.so.1.0.6/
/
(ylE�q&Ts�Y� �)�}$ block %d: crc = 0x%08x, combined CRC = 0x%08x, size = %d %d in block, %d after MTF & 1-2 coding, %d+2 syms in use initial group %d, [%d .. %d], has %d syms (%4.1f%%) pass %d: size is %d, grp uses are final combined CRC = 0x%08x %d bytes: mapping %d, selectors %d, code lengths %d, codes %d Y@ [%d: huff+mtf rt+rld�����������ܦ��D���Զ��d����4�������t�������<���,�������������������̰������4�������Ԭ��ԧ��T�������4���IJ��t������ԫ���������,�������|����t���,������� {0x%08x, 0x%08x}wr1.0.6, 6-Sept-2010OKSEQUENCE_ERRORPARAM_ERRORMEM_ERRORDATA_ERRORDATA_ERROR_MAGICIO_ERRORUNEXPECTED_EOFOUTBUFF_FULLCONFIG_ERROR??? combined CRCs: stored = 0x%08x, computed = 0x%08x
bzip2/libbzip2: internal error number %d. This is a bug in bzip2/libbzip2, %s. Please report it to me at: jseward@bzip.org. If this happened when you were using some program which uses libbzip2 as a component, you should also report this bug to the author(s) of that program. Please make an effort to report this bug; timely and accurate bug reports eventually lead to higher quality software. Thanks. Julian Seward, 10 December 2007.
*** A special note about internal error number 1007 ***
Experience suggests that a common cause of i.e. 1007 is unreliable memory or other hardware. The 1007 assertion just happens to cross-check the results of huge numbers of memory reads/writes, and so acts (unintendedly) as a stress test of your memory system.
I suggest the following: try compressing the file again, possibly monitoring progress in detail with the -vv flag.
* If the error cannot be reproduced, and/or happens at different points in compression, you may have a flaky memory system. Try a memory-test program. I have used Memtest86 (www.memtest86.com). At the time of writing it is free (GPLd). Memtest86 tests memory much more thorougly than your BIOSs power-on test, and may find failures that the BIOS doesn't.
* If the error can be repeatably reproduced, this is a bug in bzip2, and I would very much like to hear about it. Please let me know, and, ideally, save a copy of the file causing the problem -- without which I will be unable to investigate it.