From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] bunzip2 looping
Date: Mon, 6 May 2002 22:01:35 -0400 [thread overview]
Message-ID: <7c53dd83fe1d7566f3bc6a1305d1ee5e@plan9.bell-labs.com> (raw)
/sys/src/cmd/bzip2/bunzip2.c
if(onemore == 0)
break;
>> if(strm.avail_in == 0 && strm.avail_out == sizeof obuf){
>> fprint(2, "early eof\n");
>> break;
>> }
} while((e=BZ2_bzDecompress(&strm)) == BZ_OK || onemore--);
add the marked lines.
reply other threads:[~2002-05-07 2:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7c53dd83fe1d7566f3bc6a1305d1ee5e@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).