From: Matt Armstrong <marmstrong@google.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: bug: notmuch show --decrypt leads to SIGSEGV
Date: Tue, 15 Aug 2017 12:10:28 -0700 [thread overview]
Message-ID: <qf5shgswst7.fsf@google.com> (raw)
In-Reply-To: <87378sog5e.fsf@tesseract.cs.unb.ca>
David Bremner <david@tethera.net> writes:
> Matt Armstrong <marmstrong@google.com> writes:
>
>> I've been able to diagnose a SIGSEGV, and I have a workaround that
>> satisfies me. I'm unsure how to fix it, so I'll describe the problem
>> and leave it at that.
>>
>> Repro:
>>
>> % notmuch --version
>> notmuch 0.25+22~g0967e46 (a recent git @HEAD)
>> % notmuch show --format=sexp --decrypt thread:000000000002ad2c
>> -> SIGSEGV
>
> Do you have a way for people other than you to reproduce it? I assume
> not all threads are a problem for you with --decrypt?
The times I have encountered this involve email I can't reveal, so a
repro would take some work. I'm happy to try to dig out specific
details, but I'm at a slight disadvantage here due to unfamiliarity.
I didn't this notice this before, but I am getting this on stderr:
"Failed to construct pkcs7 context."
So g_mime_gpg_context_new() is returning NULL.
I am running an old Ubuntu variant. My libgmime is libgmime-2.6-dev.
Looks like nothing in the API contract for g_mime_gpg_context_new()
states that it never returns NULL. Still, it appears that libgmime is
built with ENABLE_CRYPTOGRAPHY (when I download gmime source and
debbuild it, config.h sets that macro), so I'm at a loss for why that
function would return an error.
next prev parent reply other threads:[~2017-08-15 19:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 13:31 [PATCH] crypto: gracefully handle gmime errors Jan Malakhovski
2017-08-31 13:44 ` Jan Malakhovski
2017-09-01 0:10 ` [PATCH] cli: propagate NULL from _mime_node_create, handle it in callers David Bremner
2017-09-01 20:32 ` Jan Malakhovski
2017-08-31 14:22 ` [PATCH] crypto: gracefully handle gmime errors David Bremner
2017-08-31 14:30 ` David Bremner
2017-08-15 17:37 ` bug: notmuch show --decrypt leads to SIGSEGV Matt Armstrong
2017-08-15 18:11 ` David Bremner
2017-08-15 19:10 ` Matt Armstrong [this message]
2017-08-15 23:12 ` David Bremner
2017-08-16 16:41 ` Matt Armstrong
2017-08-20 13:43 ` David Bremner
2017-08-31 15:17 ` [PATCH] crypto: gracefully handle gmime errors Jan Malakhovski
2017-08-31 18:33 ` David Bremner
2017-08-31 22:27 ` David Bremner
2017-08-31 23:20 ` Matt Armstrong
2017-08-31 23:59 ` Jan Malakhovski
2017-11-10 1:05 ` bug: notmuch show --decrypt leads to SIGSEGV David Bremner
2017-08-31 14:34 ` [BUG] gmime-3.0.1 (was: [PATCH] crypto: gracefully handle gmime errors) Jan Malakhovski
2017-09-05 10:54 ` David Bremner
2017-09-05 12:55 ` Jan Malakhovski
2017-09-05 13:38 ` David Bremner
2017-09-05 14:26 ` Jan Malakhovski
2017-09-05 15:26 ` David Bremner
2017-09-05 20:23 ` Jan Malakhovski
2017-09-05 14:04 ` Servilio Afre Puentes
2017-09-05 14:27 ` Jan Malakhovski
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=qf5shgswst7.fsf@google.com \
--to=marmstrong@google.com \
--cc=david@tethera.net \
--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).