• Check out http://bugs.clamav.net

Stuff imported from old wiki

If for some reasons ClamAV crashes please follow the steps below to file your bug report.

Assuming you get something like: user@host:~/somedir$ clamscan --some-options some_file Segmentation fault Getting a core dump

You first step is making the kernel write a core dump. For bourne-like shells (i.e. bash):

user@host:~/somedir$ ulimit -c unlimited For c-like shells (i.e. tcsh):

user@host:~/somedir> limit coredumpsize unlimited

Now the situation above should have changed to: user@host:~/somedir$ clamscan --some-options some_file Segmentation fault (core dumped)

Looking at your current working directory should reveal a file named core. Obtaining a backtrace

The next step is to load the core file into gdb (The GNU Debugger): user@host:~/somedir$ gdb -core=core --args clamscan --some-options some_file (gdb)

You should now see the gdb prompt. Just use the bt command at the prompt to make gdb print a full backtrace; copy and save it. You can use the q command to leave gdb. Filing the bug report

Visit http://www.clamav.net/bugs

To help the developers analyse the problem please add as much details as you can: Full system specs: e.g. output from uname -mrsp (or something like that) Your libc and possibly zlib versions The output from clamscan -V The steps to perform in order to reproduce the problem The backtrace obtained from gdb If the issue is reproducible only scanning a specific sample, provided it's small enough for mailing, attach it as well. Optionally, if you think it's helpful, the output from strace (not covered here)

Please use a working email address so the developers can get in touch with you to obtain additional info and notify you when the problem is fixed.

-- LucaGibelli - 15 Nov 2006

</center-->