Hmmmm.... looks like a bug, but because spamdyke is compiled C, there's almost no way to tell how it happened. If you updated your OS but didn't update spamdyke, I'd suggest making sure you're on the latest version of spamdyke and recompiling it on your updated OS. If you still see crashes, the best way to troubleshoot them would be to find a reliable way to reproduce them -- using spamdyke's "full-log-dir" option to capture the input, for example. Failing that, I could send you some updates for your Makefile to recompile spamdyke with an address sanitizer that will produce must larger (and much more informative) crash messages.
-- Sam Clippinger > On Mar 30, 2020, at 7:51 PM, Webtao via spamdyke-users > <spamdyke-users@spamdyke.org> wrote: > > Hi Sam, > > First of all, thank you for managing spamdyke :-) > > Lately, I updated my Centos 6.5 and suddenly got this error : > > *** glibc detected *** /usr/bin/spamdyke: double free or corruption > (fasttop): 0x000000000127afe0 *** > ======= Backtrace: ========= > /lib64/libc.so.6(+0x75e5e)[0x7fad8a556e5e] > /lib64/libc.so.6(+0x78cad)[0x7fad8a559cad] > /usr/bin/spamdyke[0x41e7f7] > /usr/bin/spamdyke[0x41797e] > /lib64/libc.so.6(__libc_start_main+0x100)[0x7fad8a4ffd20] > /usr/bin/spamdyke[0x402849] > > Do you have any idea to resolve this? > > Thank you for your help, Lenawaii > _______________________________________________ > spamdyke-users mailing list > spamdyke-users@spamdyke.org > https://spamdyke.org/mailman/listinfo/spamdyke-users
_______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org https://spamdyke.org/mailman/listinfo/spamdyke-users