Hello Michael Becker, unfortunately it is not enough to just install the debug information for the executable.
In your case the shared library leads us to the libsane package: # dpkg -S /usr/lib/x86_64-linux-gnu/sane/libsane-mustek_usb2.so.1 libsane:amd64: /usr/lib/x86_64-linux-gnu/sane/libsane-mustek_usb2.so.1 Unfortunately libsane has not yet a dbgsym package, but there is an old style libsane-dbg. With that installed your backtrace would be a lot more easier to read. Nevertheless, from running xsane without such a hardware and just from inspecting the assembly addresses I think this stack smashing happens somewhere in function Mustek_DMAWrite [1]. I think this is the same issue as another user reported in bug #886777. There is also a short draft how I think it could be possible to get the exact location of the overwriting. Unfortunately there I used wrongly "libsane-dbgsym" instead of "libsane-dbg". Probably thereof that user never reported back ... But probably you could give it a try? Kind regards, Bernhard #886777 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886777 [1] https://gitlab.com/sane-project/backends/blob/master/backend/mustek_usb2_asic.c#L304
