Hi guys,
I have some strange, very reproducible segfaults in clamd on a Debian-based system. I tried 0.83 and the cvs version. I built it from source with debug symbols and static libs (to simplify debugging).
Anyway, my segfaults occur only when I use clamd in a setup where I do a lot of stream scanning, from multiple threads. And they only occur on this one debian system that appears to be using TLS libraries (/lib/tls, etc). (It's not hardware as I tried the same distro on multiple machines.. even in vmware -- it's definitely related to the distro itself and maybe the tls libs?).
Examination of core files shows that ultimately one of the worker threads dies somewhere in the scandesc() function, when calling into libc. I suspect stack corruption, but I can't be sure yet..
Anyway I saw some old messages from last year about some incompatibilities between linux tls libraries (/lib/tls, et al) and clam-milter, etc.
Are there any known issues between clamd and its surrounding libraries? Since threaded apps sometimes push libraries beyond their capabilities (eg reentrantcy) I was hoping if there was anything obvious that would be causing clamd to crash hard on a linux tls-system.
BTW: What are these tls libraries anyway? Thread-local storage? Why do they break clamd?
Thanks for any help, advice, info..
-Calin
_______________________________________________ http://lurker.clamav.net/list/clamav-devel.html
