Recently, I've been getting email messages that look like this: *** stack smashing detected ***: /usr/bin/w3m terminated ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f03ee523bcb] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f03ee5ac0e7] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f03ee5ac0b0] /usr/bin/w3m(+0x54574)[0x560e882b2574] /usr/bin/w3m(+0x55974)[0x560e882b3974] /usr/bin/w3m(+0x3dd18)[0x560e8829bd18] /usr/bin/w3m(+0x3ec68)[0x560e8829cc68] /usr/bin/w3m(+0x3f076)[0x560e8829d076] /usr/bin/w3m(+0x42416)[0x560e882a0416] /usr/bin/w3m(+0x20e26)[0x560e8827ee26] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f03ee4d32b1] /usr/bin/w3m(+0x2192a)[0x560e8827f92a] ======= Memory map: ======== 560e8825e000-560e8830f000 r-xp 00000000 09:01 5511742 /usr/bin/w3m (lots more core dump lines deleted)
Am I seeing messages that are being sent from a buggy sender, or is my local /usr/bin/w3m blowing up and spewing the detritus into the mail message? This is with w3m 0.5.3-31, which appears to be the most current version in Debian testing.
