talloc_abort in notmuch_thread_get_tags () when db has been modified

Gaute Hope eg at gaute.vetsj.com
Fri Nov 3 05:02:42 PDT 2017

Gaute Hope writes on november 3, 2017 11:45:
> David Bremner writes on februar 17, 2017 16:35:
>> Gaute Hope <eg at gaute.vetsj.com> writes:
>>> threads != NULL
>>> terminate called after throwing an instance of 'Xapian::DatabaseModifiedError'
>> Yeah, that looks like a different problem. But it _should_ be something
>> we can catch in libnotmuch.
> For reference; I'm getting several reports of this or similar error:
>   * https://github.com/astroidmail/astroid/issues/414
>   * https://github.com/astroidmail/astroid/blob/master/tests/test_notmuch_standalone.cc
> Presently, I cannot reproduce it myself, but seems to be fairly 
> consistent for the users this happens with.
> Not sure if this is talloc_abort() anymore.

Actually, at this point this seems to be caused by different GMime 
versions used for binary and notmuch library. 

Regards, Gaute

More information about the notmuch mailing list