Nice! It is valgrind clean now, but the testsuite fails:
$ ./bunzip2.tests PASS: bunzip2: doesnt exist PASS: bunzip2: unknown suffix PASS: bunzip2: already exists PASS: bunzip2: stream unpack PASS: bunzip2: delete src PASS: bunzip2: test_bz2 file PASS: bunzip2: pbzip_4m_zeros file PASS: bunzip2: bz2_issue_11.bz2 corrupted example FAIL: bunzip2: bz2_issue_12.bz2 corrupted example Maybe, now that this is fixed, the issue_12 expectation should be changed? It currently expects "bunzip2: bunzip error -3:1", yet we now generate "bunzip2: bunzip error -5:1" (just like issue_11 corrupted example) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1828282 Title: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always Status in BusyBox: Fix Released Status in Ubuntu on IBM z Systems: Invalid Status in busybox package in Ubuntu: Fix Committed Status in glibc package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Get a system with glibc 2.29 2) Get busybox 1.30.1 installed (e.g. eoan, or download busybox package from https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3/+build/16724246 and use $ apt install ./busybox*.deb to install) 3) Get busybox 1.30.1 source code, e.g. $ pull-lp-source busybox Or like download the orig tarball from https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3 4) Run the bunzip2 testsuite: cd testsuite/ ECHO=/bin/echo ./bunzip2.tests Observe that with glibc 2.29 the: PASS: bunzip2: bz2_issue_11.bz2 corrupted example is XFAIL or FAIL, on s390x, whereas it passes on all other arches. If one uses glibc 2.28 (ie. use Cosmic, and install busybox & use matching test suite from eoan using links above) one can observe that the testcase always passes. We suspect this might be a glibc 2.29 s390x-specific setjmp regression. Probably due to setjmp usage in ./archival/libarchive/decompress_bunzip2.c The tests were done on a z13 machine. To manage notifications about this bug go to: https://bugs.launchpad.net/busybox/+bug/1828282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
