--=-=-=

mail-notification is crashing on post-newlock2 current, and works on
netbsd-4.  I think the problem is a lack of locking and openssl being
called on the same context in two threads.  But, I was asked about
whether openssl declares OPENSSL_THREADS, and it seems that it does not.

I had meant to send the following here instead of pkgsrc-users:


--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline

From: Greg Troxel <gdt@ir.bbn.com>
To: pkgsrc-users@netbsd.org
Subject: Re: threading bug in mail-notification?
References: <rmizm53mc15.fsf@fnord.ir.bbn.com>
Date: Fri, 20 Apr 2007 12:33:03 -0400
In-Reply-To: <rmizm53mc15.fsf@fnord.ir.bbn.com> (Greg Troxel's message of
	"Fri\, 20 Apr 2007 09\:05\:26 -0400")
Message-ID: <rmibqhj2egw.fsf@fnord.ir.bbn.com>
MIME-Version: 1.0

Greg Troxel <gdt@ir.bbn.com> writes:

> I've been using gnome mail notification applet mail/mail-notification
> under NetBSD for a while, and it works on uniprocessors under netbsd-4
> and used to work on current under MP (T60, Core Duo).  I monitor 2
> mailboxes, both IMAP/SSL.
>
> On the T60 (4.99.17), it hits an assertion at startup:
>
> assertion "md_c[1] == md_count[1]" failed: file
> "/usr/home/gdt/NetBSD-current/src/crypto/dist/openssl/crypto/rand/md_rand.c",
> line 312, function "ssleay_rand_add"
>
> It seems this is about openssl operations being invoked on a single
> context in more than one thread at once.

I've filed a bug with mail-notification about this, and was asked about
whether our openssl is built with thread support.

  https://savannah.nongnu.org/bugs/index.php?19643

Should our openssl be compiled with thread support?
Is mail-notification doing something wrong?


--=-=-=--