Hi --
(clamav 0.60, compiled on freebsd 4.8-RC, running on freebsd 4.7-STABLE)
I've got an assortment of messages that segfault clamscan when fed to
"clamscan --mbox -".
(gdb) bt
#0 0x2807b816 in messageAddArguments (m=0x8b1ba00,
string=0x2 <Error reading address 0x2: Bad address>) at message.c:283
#1 0x2807a0c6 in insert (mainMessage=0x8056000, blobsIn=0x0, nBlobs=0,
textIn=0x0, dir=0x8052060 "/var/tmp//e7626b2ecac82e6d",
rfc821Table=0x8b0ae30, subtypeTable=0x8b0ae80) at mbox.c:461
#2 0x28079c52 in cl_mbox (dir=0x8052060 "/var/tmp//e7626b2ecac82e6d", desc=0)
at mbox.c:288
#3 0x804baf3 in scanmanager (opt=0x8053030) at manager.c:197
#4 0x8049905 in clamscan (opt=0x8053030) at clamscan.c:125
#5 0x8049f5f in main (argc=3, argv=0xbfbff7b4) at options.c:147
#6 0x804953a in _start ()
The messages can be found at:
http://www.grendel.net/handler/private/clamav/
if anyone wants to look at them.
I tried debugging the failure under gdb, but I am lacking in the
thread-debugging department. :/
Is there a development release I should be trying to see if the
problems are fixed in there? I saw some previous traffic in the web
archives re: the sourceforge snapshot tarball generation being
broken; what should I work off of?
Thanks!
--
michael handler [EMAIL PROTECTED] washington, dc
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Clamav-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-devel
