Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: Kazuo Teramoto <kaz.rag@gmail.com>
To: Patrick Totzke <patricktotzke@googlemail.com>, notmuch@notmuchmail.org,
	David Bremner <david@tethera.net>
References: <877h1e6r9d.fsf@zancas.localnet>
	<1325282290-29565-1-git-send-email-kaz.rag@gmail.com>
	<20111231011647.24112.70437@brick.lan>
In-Reply-To: <20111231011647.24112.70437@brick.lan>
Date: Sat, 31 Dec 2011 01:30:28 -0000
Message-ID: <20111231013028.14545.79903@sophie>
Subject: Re: [PATCH 0/2] Multiples calls of g_mime_init
Date: Fri, 30 Dec 2011 23:30:28 -0200
Precedence: list

On 2011-12-30T23:16:47, Patrick Totzke wrote:

>It seeminly doesn't break things either and I'm all in favour of doing
>things right=E2=84=A2.

And talking about doing things right, we probably need to call
g_mime_shutdown() too, one for every time we call g_mime_init(). I will
send a patch after I do some more tests.

>On a related note: It also doesn't fix the recent segfaults of the bindings
>that occur when you try to write to a locked database.
>cf "id:4eddf2b1.4288980a.0b74.5557@mx.google.com"
>

This still hit me. If I remember right when I did a test what is
happening is that the binding is trying to close the db, so we need a
check if the db is opened before trying to close it.