Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
>
> However, if you tell me exactly (step by step) what I have to do to give
> you
> more information, I will try my best. I am very happy with ClamAV so far
> and
> I want to support it.
>
(I'm going to assume you're clamd is multithreaded. If not just do steps 1-3
followed by the command 'bt').
This may, or may not, provide some useful information.
1. Use 'ps' to get the PID of clamd:
ps -aux (or ps -elf on SysV)
clamav 24897 0.0 1.9 38032 10068 ? S Jan13 0:00 lt-clamd
^---- pid
2. Attach gdb to the running process
gdb /usr/local/bin/clamd 24897
^--- path to ^--- process id, from above
clamd binary
3. you should now get the gdb prompt, as: (gdb)
4. the command 'bt' will give a backtrace for the current thread.
The command 'info threads' will tell you how many threads there are.
The command 'thread <n>' will change to the specified thread, after which you
can use the 'bt' command again to get it's backtrace.
So, you basically want to do:
a. 'info threads' to get the number of threads and their id numbers
b. for each thread do:
thread <id number>
bt
5. exit from gdb with the 'quit' command. Reply 'y' to the question about the
program still running.
6. send a copy of the output from the above, including the clam version number
and platform (e.g. RH Linux, Solaris 9)
Cheers,
-trog
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
