From: "tiberiuzbirnea at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/27619] New: False error code returned by BZ2_bzBuffToBuffDecompress
Date: Sun, 21 Mar 2021 15:50:28 +0000 [thread overview]
Message-ID: <bug-27619-11876@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27619
Bug ID: 27619
Summary: False error code returned by
BZ2_bzBuffToBuffDecompress
Product: bzip2
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bzip2
Assignee: nobody at sourceware dot org
Reporter: tiberiuzbirnea at gmail dot com
CC: bzip2-devel at sourceware dot org
Target Milestone: ---
Version: 1.0.8
File: bzlib.c
Function: BZ2_bzBuffToBuffDecompress
Line: 1342
Actual conent: return BZ_OUTBUFF_FULL;
Should be: return BZ_OK;
Comment:
In this function the "output_overflow_or_eof" label can be reached if
"BZ2_bzDecompress" returned BZ_OK. The branch with line 1342 is reached if
strm.avail_out == 0, so th output buffer is full but nothing has to be added
anymore.
Context:
I have written a wrapper class for this version. At compression method I`ve
allocated a buffer 4 bytes larger than it is presented in documentation
"To guarantee that the compressed data will fit in its buffer, allocate an
output buffer of size 1% larger than the uncompressed data, plus six hundred
extra bytes"
to store the uncompressed data size.
At decompression I've constantly receive BZ_OUTBUFF_FULL as a result, despite
strm.avail_out == 0.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2021-03-21 15:50 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=bug-27619-11876@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=bzip2-devel@sourceware.org \
/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).