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

2017-11-03 Thread Gaute Hope 

David Bremner writes on november 3, 2017 13:18:

Gaute Hope  writes:


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


OK, that sounds like not-a-notmuch-bug.


Yes.. most definetely not.

- gaute

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

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

2017-11-03 Thread David Bremner 
Gaute Hope  writes:

>> 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

OK, that sounds like not-a-notmuch-bug.

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

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

2017-11-03 Thread Gaute Hope 

David Bremner writes on februar 17, 2017 16:35:

Gaute Hope  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

Re: Segfault with pkcs7 message

2017-11-03 Thread Jani Nikula 
On Fri, Nov 3, 2017 at 11:05 AM, Holger Schurig  wrote:
> The attached e-mail makes notmuch from git HEAD segfault:
>
> $ notmuch --version
> notmuch 0.25.1+161~g1b91884
> $ notmuch show --decrypt id:86595dab-d486-536b-fe7a-ae3e1dca1...@posteo.de
> Warning: Crypto engine initialization failure (application/pkcs7-signature).
> Segmentation fault

See http://mid.mail-archive.com/20171016154044.14564-1-jani%40nikula.org

BR,
Jani.
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Segfault with pkcs7 message

2017-11-03 Thread Holger Schurig 
The attached e-mail makes notmuch from git HEAD segfault:

$ notmuch --version
notmuch 0.25.1+161~g1b91884
$ notmuch show --decrypt id:86595dab-d486-536b-fe7a-ae3e1dca1...@posteo.de
Warning: Crypto engine initialization failure (application/pkcs7-signature).
Segmentation fault


Without the --decrypt I can see the visible text, but I'm unaware on how I
can make the elisp code not send this command line option.
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch