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 4D6BE6DE1B82 for ; Fri, 17 Feb 2017 04:28:39 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.005 X-Spam-Level: X-Spam-Status: No, score=-0.005 tagged_above=-999 required=5 tests=[AWL=0.006, 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 Uan8hyozAwgN for ; Fri, 17 Feb 2017 04:28:38 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 7FB206DE1B7D for ; Fri, 17 Feb 2017 04:28:38 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1cehdm-0003Mo-LU; Fri, 17 Feb 2017 07:27:58 -0500 Received: (nullmailer pid 13393 invoked by uid 1000); Fri, 17 Feb 2017 12:28:33 -0000 From: David Bremner To: Gaute Hope , notmuch@notmuchmail.org Subject: Re: talloc_abort in notmuch_thread_get_tags () when db has been modified In-Reply-To: <1487199120.tz5yvag0pm.astroid@strange.none> References: <1453121100-astroid-2-c62fwcrm91-18877@strange> <1457341792-astroid-0-2wtydh6y1q-15951@strange> <87r3fmts2y.fsf@zancas.localnet> <1487199120.tz5yvag0pm.astroid@strange.none> Date: Fri, 17 Feb 2017 08:28:33 -0400 Message-ID: <877f4p9f2m.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Fri, 17 Feb 2017 12:28:39 -0000 Gaute Hope writes: > David Bremner writes on mars 7, 2016 13:01: >> Gaute Hope writes: >> >> Of course _why_ this error is happening could still be notmuch's >> fault. Can you reproduce the problem under valgrind? > > Hi again, > > For future reference: Attached is C++ test code that demonstrates the problem > (at least on my setup). It is part of the astroid test suite. > And did you try running this under valgrind? > The test-code must be adapted to your _test_ notmuch db. > > To pick up on this again, this issue started cropping up more frequently > again, and I can't see a way currently to anticipate or recover from > this from a user application of the notmuch library. There seems to be > an XapianError, which may or may not be handled by notmuch. Previously you only reported a talloc error. Do you have a new stacktrace?