Re: Bug#1067639: sasl2-bin: terminates with smashed stack
Eero Tamminen <[email protected]>
| Newsgroups | gmane.linux.debian.ports.68k |
|---|---|
| Message-ID | <[email protected]> |
Hi, On 25.3.2024 0.03, Thorsten Glaser wrote: >> I was able to strace this: ... > (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 ?? () > > > Unfortunately, gdb *generally* does not seem to be helpful: Does "strace -f -k" show useful backtrace for the assert message output syscall? - Eero