Date: Sun, 4 Dec 2011 13:29:49 -0500
From: Austin Clements <amdragon@MIT.EDU>
To: David Bremner <david@tethera.net>
Subject: Re: notmuch seg. fault on _thread_add_message
Message-ID: <20111204182948.GU16194@mit.edu>
References: <20111204173539.GA4411@sophie>
 <87r50kurv1.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87r50kurv1.fsf@zancas.localnet>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: notmuch@notmuchmail.org
Precedence: list

Quoth David Bremner on Dec 04 at  2:14 pm:
> On Sun, 4 Dec 2011 15:35:39 -0200, Kazuo Teramoto <kaz.rag@gmail.com> wrote:
> > Hi!
> > 
> > Following an alot bug report [1] I created a small python script that
> > causes a segmentation fault in notmuch:
> > ========================================================================
> > #!/usr/bin/env python2
> > import notmuch
> > db = notmuch.Database(mode=notmuch.Database.MODE.READ_WRITE)
> > q_new = notmuch.Query(db, 'tag:inbox')
> > for t in q_new.search_threads():
> >     pass
> > ========================================================================
> 
> As I mentioned previously, I suspect the message below should be fixed;
> whether or not it fixes your bug I don't know. I'm not sure where
> exactly g_type_init would/should be called in the library; there isn't
> currently a global initialization call for libnotmuch. Perhaps there
> should be?

I believe g_type_init can be safely called multiple times, which means
we could call it in notmuch_database_open.