[Bug 1828282] Re: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always
Dimitri John Ledkov
launchpad at surgut.co.uk
Wed May 15 13:55:05 UTC 2019
@IBM
Please close your LTC bugzilla entry. We will continue to use this LP issue to pursue busybox upstream. Thanks a lot for your input!
** Changed in: busybox (Ubuntu)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1828282
Title:
busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always
Status in Ubuntu on IBM z Systems:
Invalid
Status in busybox package in Ubuntu:
Triaged
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/ubuntu-z-systems/+bug/1828282/+subscriptions
More information about the foundations-bugs
mailing list