[sanesecurity] Re: clamd stability & fetch-sanesecurity-sigs
- From: Tomasz Kojm <tkojm@xxxxxxxxxx>
- To: sanesecurity@xxxxxxxxxxxxx
- Date: Tue, 27 Jan 2009 18:30:41 +0100
On Tue, 27 Jan 2009 12:59:51 +0000
Gareth <list-mailscanner@xxxxxxxxxxxxxxx> wrote:
> On Mon, 2009-01-26 at 08:45, Steve Basford wrote:
> > Everyone getting crashes, please read this, to help debug:
> >
> > http://www.clamav.net/bugs/lang-pref/en/
> >
> > And post results/info into this entry:
> >
> > https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1370
>
> I eventually got another crash and this time I had gdb running and was
> able to do a backtrace. Bugzilla has been updated and I have also posted
> the backtrace below incase anyone is interested.
>
> Program received signal SIGSEGV, Segmentation fault.
> cli_ac_free (root=0xb58fe730) at matcher-ac.c:351
> 351 patt->prefix ? free(patt->prefix) : free(patt->pattern);
> (gdb) bt
> #0 cli_ac_free (root=0xb58fe730) at matcher-ac.c:351
> #1 0x00122880 in cl_free (engine=0xb7e00a48) at readdb.c:2131
> #2 0x0804e91d in reload_db (engine=0xb09633f8, dboptions=26, copt=<value
> optimized out>, do_check=0, ret=0xbfd25558) at server-th.c:243
> #3 0x0804f265 in acceptloop_th (socketds=0xbfd2564c, nsockets=1,
> engine=0xb7e00a48, dboptions=26, copt=0x8fbf5d8) at server-th.c:674
> #4 0x0804d184 in main (argc=Cannot access memory at address 0x1
> ) at clamd.c:479
Would it be possible for you to run clamd under valgrind and wait for another
crash? (valgrind -v /usr/local/sbin/clamd) Hopefully this would provide us more
information about the nature of the problem
--
oo ..... Tomasz Kojm <tkojm@xxxxxxxxxx>
(\/)\......... http://www.ClamAV.net/gpg/tkojm.gpg
\..........._ 0DCA5A08407D5288279DB43454822DC8985A444B
//\ /\ Tue Jan 27 18:30:34 CET 2009
Other related posts:
