[Bug 11896] New: bunzip2: bunzip fails testsuite on s390x Conditional jump or move depends on uninitialised value(s)
bugzilla at busybox.net
bugzilla at busybox.net
Thu May 23 10:56:10 UTC 2019
https://bugs.busybox.net/show_bug.cgi?id=11896
Bug ID: 11896
Summary: bunzip2: bunzip fails testsuite on s390x Conditional
jump or move depends on uninitialised value(s)
Product: Busybox
Version: 1.30.x
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at busybox.net
Reporter: xnox at ubuntu.com
CC: busybox-cvs at busybox.net
Target Milestone: ---
Originally reported at
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1828282 with initial
suspicion at glibc, however later diagnosed to be a busybox issue.
The full analysis is at
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1828282/comments/1
In short bz2_issue_11.bz2 test case always fails on s390x since bunzip2 depends
on uninitialised values, which happen to always be "wrong" on s390x.
This is observable with valgrind too:
# valgrind busybox bunzip2 <bz2_issue_11.bz2 2>&1 >/dev/null
==40965== Memcheck, a memory error detector
==40965== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==40965== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==40965== Command: busybox bunzip2
==40965==
==40965== Conditional jump or move depends on uninitialised value(s)
==40965== at 0x17C1D4: get_next_block (decompress_bunzip2.c:393)
==40965== by 0x17C37F: get_next_block (decompress_bunzip2.c:419)
==40965==
bunzip2: bunzip error -5
==40965==
==40965== HEAP SUMMARY:
==40965== in use at exit: 0 bytes in 0 blocks
==40965== total heap usage: 7 allocs, 7 frees, 4,539,696 bytes allocated
==40965==
==40965== All heap blocks were freed -- no leaks are possible
==40965==
==40965== For counts of detected and suppressed errors, rerun with: -v
==40965== Use --track-origins=yes to see where uninitialised values come from
==40965== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
For the time being we are skipping the bz2_issue_11.bz2 test case in ubuntu.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list