From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Bug in lrzip 0.631-1 (32 bit version) with -d -o - options
Date: Sun, 05 Feb 2017 06:40:00 -0000 [thread overview]
Message-ID: <5787b681-2927-9067-d7da-70c0e9a29c93@gmail.com> (raw)
In-Reply-To: <CAPJ9Yc8SQ_btEtyrZhqR22W4AUY1=xveQnM1_A0ENdyUUEgP=A@mail.gmail.com>
On 25/01/2017 23:15, David Balažic wrote:
> Hi!
>
> The 32 bit version of lrzip 0.631-1 contains a bug that corrupts the
> decompressed dat in some circumstances.
>
> I reproduced the problem on 2 PCs (the md5sum of the broken output was
> the same on both systems).
>
> I seems to happen when the (de)compressed file size is bigger than the
> available RAM (note that the 32 bit version uses max 4GB in any case)
> and lrzip resorts to using a temporary file.
>
[cut]
>
>
> Simply decompressing the file (lrzip -d -o sda.img sda.img.lrz2) to
> filesystem works fine, only when piped to stdout the problem happens.
>
> The 64 bit version does not have this problem.
>
>
>
> Regards,
> David
>
can you check if latest cygwin test solves the issue ?
There was a change on pipe handling.
https://cygwin.com/ml/cygwin-announce/2017-02/msg00007.html
- Always try to write all incoming bytes to blocking pipes, as required
by POSIX.
Addresses: https://cygwin.com/ml/cygwin/2017-01/msg00087.html
Regards
Marco
--
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
next prev parent reply other threads:[~2017-02-05 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 22:16 David Balažic
2017-01-30 15:23 ` David Balažic
2017-02-01 21:25 ` David Balažic
2017-02-05 1:25 ` David Balažic
2017-02-05 6:40 ` Marco Atzeri [this message]
2017-02-05 14:19 ` David Balažic
2017-05-31 14:16 ` David Balažic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5787b681-2927-9067-d7da-70c0e9a29c93@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).