From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id DA7A76DE009B for ; Tue, 15 Aug 2017 16:12:10 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bdpmvULybLrd for ; Tue, 15 Aug 2017 16:12:09 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id AEFC26DE0005 for ; Tue, 15 Aug 2017 16:12:09 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1dhkws-0006JA-OC; Tue, 15 Aug 2017 19:08:34 -0400 Received: (nullmailer pid 1260 invoked by uid 1000); Tue, 15 Aug 2017 23:12:04 -0000 From: David Bremner To: Matt Armstrong , notmuch@notmuchmail.org Subject: Re: bug: notmuch show --decrypt leads to SIGSEGV In-Reply-To: References: Date: Tue, 15 Aug 2017 20:12:04 -0300 Message-ID: <877ey4juij.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Aug 2017 23:12:11 -0000 Matt Armstrong writes: > David Bremner writes: > >> Matt Armstrong 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. > Understood. If you manage to bisect the commit that introduces the problem (I suspect the rearrangement to support gmime-3.0, but you never know), that might be helpful. d