From: David Bremner <david@tethera.net>
To: Kazuo Teramoto <kaz.rag@gmail.com>, notmuch@notmuchmail.org
Subject: Re: notmuch seg. fault on _thread_add_message
Date: Sun, 04 Dec 2011 14:14:10 -0400 [thread overview]
Message-ID: <87r50kurv1.fsf@zancas.localnet> (raw)
In-Reply-To: <20111204173539.GA4411@sophie>
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()
>
next prev parent reply other threads:[~2011-12-04 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 17:35 notmuch seg. fault on _thread_add_message Kazuo Teramoto
2011-12-04 18:14 ` David Bremner [this message]
2011-12-04 18:29 ` Austin Clements
2011-12-04 19:35 ` [PATCH] lib: call g_type_init from notmuch_database_open David Bremner
2011-12-05 1:54 ` [PATCH] test: add tests for python bindings David Bremner
2011-12-05 22:11 ` David Bremner
2011-12-05 20:55 ` [PATCH] lib: call g_type_init from notmuch_database_open bjoernb
2011-12-06 3:53 ` Proposed bug fix release 0.10.2 David Bremner
2011-12-06 11:16 ` [PATCH] lib: call g_type_init from notmuch_database_open Sebastian Spaeth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r50kurv1.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=kaz.rag@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).