Bug#1008846: motion aborts with stack smashing detected

[Pelzi]

Package: motion
Version: 4.3.2-1 armhf

Dear maintainer,

Motion does not start anymore after an update, it aborts with a stack smashing message:


$ sudo -u motion motion
*** stack smashing detected ***: terminated
Abgebrochen



Generating a core and analysing the stack trace with gdb yields:

Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `motion'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden.
(gdb) where
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7522f804 in __GI_abort () at abort.c:79
#2 0x75281af4 in __libc_message (action=action@entry=do_abort, fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:155
#3 0x75303f10 in __GI___fortify_fail (msg=0x7534f358 "stack smashing detected") at fortify_fail.c:26
#4 0x75303eec in __stack_chk_fail () at stack_chk_fail.c:24
#5 0x75bf99e0 in msmpeg4v2_encode_motion (s=0x74c41e6c, val=<optimized out>) at src/libavcodec/msmpeg4enc.c:374
#6 0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


The behaviour is reproducible, it happens at any startup.

Package version and dependency:
$ dpkg-query --show -f '${Package} ${Version} ${Depends}\n' motion libavcodec58
libavcodec58 7:4.3.3-0+rpt3+deb11u1 libaom0 (>= 1.0.0), libavutil56 (= 7:4.3.3-0+rpt3+deb11u1), libc6 (>= 2.29), libcairo2 (>= 1.2.4), libcodec2-0.9 (>= 0.9.2), libdav1d4 (>= 0.2.1), libglib2.0-0 (>= 2.12.0), libgsm1 (>= 1.0.18), liblzma5 (>= 5.1.1alpha+20120614), libmp3lame0 (>= 3.100), libopenjp2-7 (>= 2.0.0), libopus0 (>= 1.1), libraspberrypi0, librsvg2-2 (>= 2.14.4), libshine3 (>= 3.1.0), libsnappy1v5 (>= 1.1.8), libspeex1 (>= 1.2~beta3-1), libswresample3 (= 7:4.3.3-0+rpt3+deb11u1), libtheora0 (>= 1.0), libtwolame0 (>= 0.3.10), libudev1 (>= 183), libva2 (>= 2.2.0), libvorbis0a (>= 1.1.2), libvorbisenc2 (>= 1.1.2), libvpx6 (>= 1.6.0), libwavpack1 (>= 4.40.0), libwebp6 (>= 0.5.1), libwebpmux3 (>= 0.6.1-2.1), libx264-160 (>= 2:0.160.3011+gitcde9a93), libx265-192 (>= 3.2), libxvidcore4 (>= 1.2.2), libzvbi0 (>= 0.2.35), zlib1g (>= 1:1.2.0)
motion 4.3.2-1 libavcodec58 (>= 7:4.2), libavdevice58 (>= 7:4.0), libavformat58 (>= 7:4.2), libavutil56 (>= 7:4.0), libc6 (>= 2.28), libjpeg62-turbo (>= 1.3.1), libmariadb3 (>= 3.0.0), libmicrohttpd12 (>= 0.9.50), libpq5, libsqlite3-0 (>= 3.6.0), libswscale5 (>= 7:4.0), debconf (>= 0.5) | debconf-2.0, lsb-base (>= 3.0-6), adduser

[Bernhard Übelacker]

Dear Maintainer,
this crash looks like it happens with a raspberry pi 2 or 3,
running some official 32-Bit raspios image, at least the referenced
libavcodec58 version seems to from here [1].

I currently have no real hardware at hand, so I tried emulating it,
but this failed with the 32-bit kernel, as I wanted to use a v4l2loopback
device to feed into motion, so could not reproduce the stack smashing here.

As this binary package is not controlled by Debian I am not
even sure this is the right place to report this issue.

Kind regards,
Bernhard

[1] http://archive.raspberrypi.org/debian/pool/main/f/ffmpeg/libavcodec58_4.3.3-0+rpt3+deb11u1_armhf.deb