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