tags 729941 + upstream - moreinfo # documentation severity 729941 minor quit
Eduard Bloch wrote: > As far as I remember, zlib always > returned ..._END when the result stream was completely written into the > output buffer. And I have seen liblzma behaving the same way but it's > not the case for the mentioned file(s) according to gdb. Here, the > returned data (n time return buffer size plus one incomplete buffer) > summs up to the total size of the stream but in the last cycle lzma_code > returns LZMA_OK and not LZMA_STREAM_END. Maybe it will become > LZMA_STREAM_END the next time when lzma_code is called but why should we > do the extra round? Ah, so the confusing behavior is that an LZMA_OK result neither guarantees that there's more output coming nor that there's no more output coming? Ok. [...] > * Jonathan Nieder [Mon, Dec 09 2013, 02:37:05PM]: >> Any idea how this could be documented better to help people running >> into this in the future? > > Maybe it should state that one has to wait for LZMA_STREAM_END to be > returned (or any !=LZMA_OK for errors) and not to add other funny > checks for input/output buffer state. Makes sense. Will think more and hopefully send a patch soon. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
