[sanesecurity] Re: clamd stability & fetch-sanesecurity-sigs

  • From: Ryan Moore <ryan.moore@xxxxxxxxxxx>
  • To: sanesecurity@xxxxxxxxxxxxx
  • Date: Mon, 26 Jan 2009 15:14:15 -0500

This is what I just got on a console after starting up gdb:

------------
Program received signal SIGUSR2, User defined signal 2.
[Switching to Thread -1211455168 (LWP 9038)]
0xb7e4eece in accept () from /lib/libpthread.so.0
(gdb)
Continuing.

Program received signal SIGSEGV, Segmentation fault.
cli_ac_free (root=0xb4923068) at matcher-ac.c:351
351             patt->prefix ? free(patt->prefix) : free(patt->pattern);
(gdb)
Continuing.

------------
I issued a few -USR2 reloads to clamd to see if I could force it to crash, but it seemed to reload just fine. I'm guessing it only crashes on a reload when new signatures are detected. However I moved a single sig file out of the dbdir and reloaded and it did crash with the same error as above (except root=0xb63ac928), took a few tries. This was all without the spam.ldb sig file being in place/installed as well. 

I'm still waiting for my email for bugzilla so I haven't posted it there yet.


Ryan Moore
----------
Perigee.net Corporation
704-849-8355 (sales)
704-849-8017 (tech)
www.perigee.net



-------- Original Message  --------
Subject: [sanesecurity] Re: clamd stability & fetch-sanesecurity-sigs
From: Bill Landry <bill@xxxxxxxxxxx>
To: sanesecurity@xxxxxxxxxxxxx
Date: Mon 26 Jan 2009 12:21:48 PM EST


Gareth wrote:

On Mon, 2009-01-26 at 08:45, Steve Basford wrote:

Hi All,

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 am getting the following when the signatures are updated.

Program received signal SIGUSR2, User defined signal 2.
[Switching to Thread -1208478016 (LWP 24200)]
0x00110402 in __kernel_vsyscall ()
(gdb) continue
Continuing.

Anyone know if gdb can be told to automatically continue in this case?
Oviously having it pause waiting for me to tell it to continue could
mean any file locking or other issue is cleared by the time I enter the
command. It would be better if I could get it to auto continue.

Thanks


Yeah, I'm seeing the same thing.  Kind of a pain as it virtually takes
clamd out of service until you either type in "continue" or "quit".

Bill



--

Ryan Moore
----------
Perigee.net Corporation
704-849-8355 (sales)
704-849-8017 (tech)
www.perigee.net

Other related posts:

  1. Home
  2. sanesecurity
  3. Archive
  4. 01-2009