Re: thread leakage

From: Daniel Black <daniel.subs_at_internode.on.net>
Date: Mon, 14 Mar 2011 23:35:45 +1100

On Monday 14 March 2011 20:55:29 Andreas Schulze wrote:
>
> How do I do this in deatail ?
> do I need a binary with debug-symbols ?

Would help. gdb -p {pid} and the btfull.

Since not enabling libunbound I haven't had a leak.

$ opendkim -V
opendkim: OpenDKIM Filter v2.3.0
        Compiled with OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
        SMFI_VERSION 0x2
        Supported signing algorithms:
                rsa-sha1
                rsa-sha256
        Supported canonicalization algorithms:
                relaxed
                simple
        Active code options:
                USE_DB
                USE_LUA
                _FFR_REPORT_INTERVALS
                _FFR_STATS
                _FFR_STATSEXT
        libopendkim 2.3.0:

I've restarted an unbound version on another server to attempt a backtrace.
opendkim -V
opendkim: OpenDKIM Filter v2.2.2
        Compiled with OpenSSL 0.9.8o 01 Jun 2010
        SMFI_VERSION 0x1000001
        libmilter version 1.0.1
        Supported signing algorithms:
                rsa-sha1
                rsa-sha256
        Supported canonicalization algorithms:
                relaxed
                simple
        Active code options:
                USE_DB
                USE_LUA
                USE_UNBOUND
                _FFR_REPORT_INTERVALS
                _FFR_STATS
                _FFR_STATS_I
                _FFR_STATSEXT
        libopendkim 2.2.2:
Received on Mon Mar 14 2011 - 12:34:47 PST