On Mon, Apr 13, 2009 at 19:26, Jay Deiman <j...@splitstreams.com> wrote: > Jay Deiman wrote: >> Török Edwin wrote: [snip] >>> Also there is some info here on how to trace leaks on FreeBSD: >>> http://keramida.wordpress.com/2008/10/15/extracting-useful-info-from-freebsd-malloc-tracing/ >>> Unfortunately that trace only gives you the timestamp when the memory >>> was allocated, and not source lines. >>> However if you turn on LogClean and LogTime in clamd, you may be able to >>> match the leaks to files that were scanned at the time. >>> >>> Then you can try scanning only those files, and see if you can reproduce >>> the leak. >> >> Cool, there's an addition to ktrace I didn't know about. I will set >> this up on one of the hosts and see what I can figure out. Hopefully I >> will be able to report back with some good information later on today. > > Well, *I* couldn't find much of any use in the ktrace output. However, > if someone else would like to take a look at the trace file, I've made > it available at: > > http://janus.splitstreams.com/clamav-ktrace.out.bz2 > > It is about 91MB compressed.
Can you run this command, and make the output available at the same location? (as described in that article linked above): $ kdump -T -f ktrace.out | ./alloctrace.py P.S. the alloctrace.py script is available at http://keramida.wordpress.com/2008/10/15/extracting-useful-info-from-freebsd-malloc-tracing/ Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
