Hello!
I'm currently testing the last snapshot 20110313. I've found something
curious.
% uname -a
CYGWIN_NT-5.1 JUPITER043890 1.7.9s(0.236/5/3) 20110313 16:22:37 i686 Cygwin
% bzip2 -cd < gcc-4.5.2.tar.bz2 > /tmp/1
% wc /tmp/1
11426953 43063570 448358400 /tmp/1
% rm /tmp/1
% cat gcc-4.5.2.tar.bz2 | bzip2 -cd > /tmp/1
cat: write error: File too large
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: No error
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
%
The command without "cat" is ok; the command with "cat" fails.
Of course, /tmp has enough free storage to contain the 448358400 bytes needed.
If the xxx.bz2 is smaller, no problem is shown.
I have not been able to reproduce this on the previous snapshot (the 2nd of
20110309), nor on the regular 1.7.8-1. For all the tests, i used the very
same gcc-4.5.2.tar.bz2 which is the one that you can get on the internet,
with cksum=4013419598.
I've another Windows XP, also 2002 SP3 and the problem does not show up here
(same cygwin installation of course). Need more investigation i suppose...
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple