Re: talloc_abort in notmuch_thread_get_tags () when db has been modified

Subject: Re: talloc_abort in notmuch_thread_get_tags () when db has been modified

Date: Fri, 03 Nov 2017 11:45:42 +0100

To: David Bremner, notmuch@notmuchmail.org

Cc:

From: Gaute Hope


David Bremner writes on februar 17, 2017 16:35:
> Gaute Hope <eg@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.

Regards, Gaute

_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Thread: