dansguardian unusable because of frequent segfaults

DawgG · l33t Joined: 17 Sep 2003 Posts: 874

i just had to deactivate dansguardian because it segfaults all the time and performance degrades frequently so users complain rightfully.

cach0rr0 · Posted: Fri Oct 08, 2010 8:49 am Post subject:

all i know to do here is snag a backtrace, and file a bug.

You familiar with that process?

You will first need to re-merge the package with FEATURES="splitdebug"
Then emerge gdb if you don't have it already

You should be able to get the numeric process ID for dansguardian with ps

fire up gdb
attach <process id>

wait for segfault, soon as it occurs, hit bt and press enter. Take that backtrace, and either post here to get other eyes on it, or, see if you can find a similar crash in an open bug.

Beyond that I don't know, as I don't use it.

(NOTE: I'm more accustomed to cdb/windbg under Windows, so I'm not entirely sure if that's the "correct" way to do things on Linux, but it's worked for me on other apps !)
_________________
Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash

DawgG · l33t Joined: 17 Sep 2003 Posts: 874

thx for your help, but i don't know if i can do that since this is a really busy production server. until i go to work on a sunday i think i can live w/out dansguardian for some time :wink:
when the opportunity occurs i will do it.
_________________
DUMM KLICKT GUT.

cach0rr0 · Posted: Fri Oct 08, 2010 8:01 pm Post subject:

ah right. yeah, suppose that's a bit of a monkey wrench!

I guess the other possibility is seeing how much of that setup you can recreate on a VM, but that gets into the territory of "wait a minute...do I really have the time to spend duplicating a setup to try and debug an issue I don't really have time to debug, for a product that isn't mind?"

but if you DO have the time/spare cycles, that'd be one path.
_________________
Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash