[Debian-med-packaging] Bug#993770: dazzdb: autopkgtest failure with glibc 2.32
Graham Inggs
ginggs at debian.org
Mon Sep 6 10:59:44 BST 2021
Source: dazzdb
Version: 1.0+git20201103.8d98c37-1
Severity: serious
Forwarded: https://github.com/thegenemyers/DAZZ_DB/issues/41
X-Debbugs-CC: debian-ci at lists.debian.org
User: debian-ci at lists.debian.org
Usertags: needs-update
Hi Maintainer
Since the upload of glibc 2.32-1 to unstable, dazzdb's autopkgtests fail [1].
autopkgtest [05:31:22]: test run-unit-test: [-----------------------
/tmp/autopkgtest-lxc.mrzrjkw_/downtmp/build.u1T/src/debian/tests/run-unit-test:
line 53: 622 Segmentation fault DBstats -mdust G > result
autopkgtest [05:31:24]: test run-unit-test: -----------------------]
autopkgtest [05:31:24]: test run-unit-test: - - - - - - - - - -
results - - - - - - - - - -
run-unit-test FAIL non-zero exit status 139
The test log shows a segfault in DBstats. Further investigation in
the upstream bug report shows this is caused by an invalid read which
could already be detected with glibc 2.31, but did not crash.
Regards
Graham
[1] https://ci.debian.net/packages/d/dazzdb/testing/amd64/
More information about the Debian-med-packaging
mailing list