Bug#1067639: sasl2-bin: terminates with smashed stack and kills qemu-user?!

[Thorsten Glaser]

Package: sasl2-bin
Version: 2.1.28+dfsg1-5
X-Debbugs-Cc: ***@mirbsd.de, debian-***@lists.debian.org

The openldap build on an m68k qemu-user buildd cannot install sasl2-bin in =
the chroot:

[=E2=80=A6]
Setting up pkg-config:m68k (1.8.1-1) ...
Setting up libsasl2-2:m68k (2.1.28+dfsg1-5) ...
Setting up libsasl2-modules-gssapi-mit:m68k (2.1.28+dfsg1-5) ...
Setting up unixodbc-dev:m68k (2.3.12-1+b1) ...
Setting up libgnutls28-dev:m68k (3.8.3-1.1+b2) ...
Setting up libhcrypto5t64-heimdal:m68k (7.8.git20221117.28daf24+dfsg-5+b2) =
=2E..
Setting up libotp0t64-heimdal:m68k (7.8.git20221117.28daf24+dfsg-5+b2) ...
Setting up db-util (5.3.3) ...
Setting up bind9-libs:m68k (1:9.19.21-1+b1) ...
Setting up libsl0t64-heimdal:m68k (7.8.git20221117.28daf24+dfsg-5+b2) ...
Setting up sasl2-bin (2.1.28+dfsg1-5) ...
*** stack smashing detected ***: terminated
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted
dpkg: error processing package sasl2-bin (--configure):
installed sasl2-bin package post-installation script subprocess returned e=
rror exit status 134
Setting up libperl-dev:m68k (5.38.2-3.2+b1) ...
Setting up libsasl2-dev (2.1.28+dfsg1-5) ...
Setting up libgssrpc4t64:m68k (1.20.1-6+b1) ...
Setting up libhx509-5t64-heimdal:m68k (7.8.git20221117.28daf24+dfsg-5+b2) .=
=2E.
dpkg: dependency problems prevent configuration of sbuild-build-depends-mai=
n-dummy:
sbuild-build-depends-main-dummy depends on sasl2-bin; however:
Package sasl2-bin is not configured yet.

dpkg: error processing package sbuild-build-depends-main-dummy (--configure=
):
dependency problems - leaving unconfigured
[=E2=80=A6]
Unpacking sbuild-build-depends-dose3-dummy (0.invalid.0) ...
Setting up sasl2-bin (2.1.28+dfsg1-5) ...
BDB0002 __fop_file_setup: Retry limit (100) exceeded
saslpasswd2: generic failure
dpkg: error processing package sasl2-bin (--configure):
installed sasl2-bin package post-installation script subprocess returned e=
rror exit status 1
[=E2=80=A6]

See: https://buildd.debian.org/status/fetch.php?pkg=3Dopenldap&arch=3Dm68k&=
ver=3D2.5.16%2Bdfsg-2%2Bb2&stamp=3D1711312418&raw=3D0

This does not seem to be specific to one buildd.
Any idea how this can be debugged?

[Eero Tamminen]

Hi,
...

(gdb) run -c 'no:such:user' <exclam
Starting program: /usr/sbin/saslpasswd2 -c 'no:such:user' <exclam
*** stack smashing detected ***: terminated
Program received signal SIGABRT, Aborted.
0xc00d1a88 in ?? ()
(gdb) bt
#0 0xc00d1a88 in ?? ()
#1 0xefffef8c in ?? ()
#2 0x00000000 in ?? ()

Does "strace -f -k" show useful backtrace for the assert message output
syscall?


- Eero

[Thorsten Glaser]

any idea?