Re: notmuch seg. fault on _thread_add_message

Subject: Re: notmuch seg. fault on _thread_add_message

Date: Sun, 04 Dec 2011 14:14:10 -0400

To: Kazuo Teramoto, notmuch@notmuchmail.org

Cc:

From: David Bremner

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?

> 
> (process:16579): GLib-GObject-CRITICAL **: gtype.c:2715: You forgot to call g_type_init()
>

Thread: