Reading .bz2 files fails to decompress or segfaults

This was tested using the 1.0.0 conda build (is this one just the wrapped static build?) as well as with several different 'static' and containerized versions from 0.9 to 1.0.1.

In all cases loading of data failed at the same step but depending on the version and how it was compiled two errors were seen:

...
[Wed 31-07-2019 11:24:23] Line 13: Created & opened temporary file /tmp/preprocessed.singles...fq12609-4.gz
/.singularity.d/runscript: line 3: 12609 Segmentation fault      (core dumped) ngless "$@"

and

...
[Wed 31-07-2019 11:23:51] Line 13: Created & opened temporary file /tmp/preprocessed.singles...fq8945-4.gz
Exiting after internal error. If you can reproduce this issue, please run your script with the --trace flag and report a bug at http://github.com/ngless-toolkit/ngless/issues
user error (BZ2_bzDecompress: -1)

We didn't try the docker containers but those also make use of the static builds so they should be equally affected.

I also tried using the same binary on the bz2 files in our testsuite and all worked fine which hints at some buffer or filesize related issue.

Currently in the process of creating a bz2 file that is big enough to trigger the error locally. If not too big I'll add this to the testsuite.

Credits to @jakob-wirbel for finding this bug.

Start by reproducing the failure with the affected .bz2 input and the testsuite data, using the --trace flag as requested in the issue. Compare behavior across the static and conda builds, then add a sufficiently large reproducer to the testsuite if feasible; done means large .bz2 files decompress without an internal error or segmentation fault.