Brian Bruns wrote:
The issue with return codes in 1.5.13 was fixed in a 1.5.14 snapshot which is what this user is using. I know all about the return code issue, and was ready to fork the Cygwin source code to fix it if they didn't fix it themselves. With the latest snapshots, everything is returning the right codes again
Strange, from Cygwin users' mail list it didn't seemed that anything was going to be changed on this issue.
So, I still have the issue where I need to find out what is causing the dumps in ClamAV. Back to square one. I have noone else reporting this issue currently.
I have the CommuniGate server running with a snapshot from back in January 29, sockets didn't work at all after that date (but that snapshot fixed the problem with all the port connections left open). On my development machine I have the 1.5.13 release with clamav-0.83 both compiled and downloaded from Cygwin, the socket problem was fixed in between. No problems at all with clamav (tested: clamd, freshclam, clamscan, and clamdscan) on both machines, and both use the dynamic library.
The only way to see what is causing the core dump is running clamscan under gdb; a workaround is to install everything you need again.
Latest cygwin snapshots are here if you need the latest DLL: http://www.cygwin.com/snapshots/
Those are too dangerous, I know, I've used snapshots and they fix something and usually break something else... well it's the same with the "stable" releases, not much testing is done. The fastest fix is usually to go back to an earlier version of whatever caused the problem (see the install log for a list of what has been changed lately).
If you need a list of packages/versions that do work I can provide it.
Regards. -- René Berber
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
