[sanesecurity] Re: clamd stability & fetch-sanesecurity-sigs
- From: Bill Landry <bill@xxxxxxxxxxx>
- To: sanesecurity@xxxxxxxxxxxxx
- Date: Mon, 26 Jan 2009 09:21:48 -0800
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
Other related posts:
