Hello Trog,
running clamd through gdb results in this backtrace:
(gdb) run
Starting program: /usr/local/sbin/clamd
[New Thread 1024 (LWP 23563)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 23563)]
0x4004e33f in inflate_codes () from /usr/local/lib/libclamav.so.1
(gdb) bt
#0 0x4004e33f in inflate_codes () from /usr/local/lib/libclamav.so.1
#1 0x4004d213 in inflate_blocks () from /usr/local/lib/libclamav.so.1
#2 0x4004c3a6 in inflate () from /usr/local/lib/libclamav.so.1
#3 0x400483f7 in gzread () from /usr/local/lib/libclamav.so.1
#4 0x40022031 in cli_untgz (fd=8, destdir=0x8053850
"/tmp/clamav-41b8dee6a45bdfaf") at cvd.c:62
#5 0x40022b29 in cli_cvdload (fd=0x8054ec8, root=0x805bfb0,
signo=0x805bfb0, warn=8) at cvd.c:418
#6 0x40020f98 in cl_loaddb (filename=0x8053828
"/usr/local/share/clamav/daily.cvd", root=0xbffff89c, signo=0xbffff8a0) at
readdb.c:708
#7 0x400218bb in cl_loaddbdir (dirname=0x8052aa8
"/usr/local/share/clamav", root=0xbffff89c, signo=0xbffff8a0) at
readdb.c:773
#8 0x0804bde9 in clamd (opt=0x8052830) at clamd.c:259
#9 0x0804b825 in main (argc=1, argv=0xbffff9e4) at options.c:114
#10 0x4026c17d in __libc_start_main (main=0x804b6b0 <main>, argc=1,
ubp_av=0xbffff9e4, init=0x8049960 <_init>, fini=0x804f2c4 <_fini>,
rtld_fini=0x4000a534 <_dl_fini>, stack_end=0xbffff9dc) at
../sysdeps/generic/libc-start.c:129
(gdb)
Never used gdb before, so this doesn't make much sense to me (yet).
Hopefully you (or someone else ;-) can make anything out of this
and explain what's wrong.
Thanks,
AK
> On Tue, 2004-12-14 at 15:33, [EMAIL PROTECTED] wrote:
>> After upgrading from clamav-0.75.1 to clamav-0.80 (slackware,
>> gcc-2.95.3)
>> all I get when starting clamd is: Segmentation fault.
>> While upgrading all looked ok, there were no errors. The log shows:
>>
>> Tue Dec 14 16:06:47 2004 -> +++ Started at Tue Dec 14 16:06:47 2004
>> Tue Dec 14 16:06:47 2004 -> clamd daemon 0.80 (OS: linux-gnu, ARCH:
>> i386,
>> CPU: i686)
>> Tue Dec 14 16:06:47 2004 -> Log file size limited to 1048576 bytes.
>> Tue Dec 14 16:06:47 2004 -> Verbose logging activated.
>> Tue Dec 14 16:06:47 2004 -> Running as user defang (UID 999, GID 106)
>> Tue Dec 14 16:06:47 2004 -> Reading databases from
>> /usr/local/share/clamav
>>
>> Has anybody seen this before and/or know how to sove this?
>
> Run clamd under gdb and do a backtrace - you will probably want to run
> it with the Foreground option set in clamd.conf, otherwise you are
> unlikely to get any significant results.
>
> -trog
>
> _______________________________________________
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
