From b54e2bcfb39248e6255e19efe24b60421cf88b6f Mon Sep 17 00:00:00 2001 From: Vladimir Marek Date: Wed, 17 Apr 2013 10:53:54 +0200 Subject: [PATCH] Re: crash during saving --- f4/dc2f3f4459d885c075db3a536ae05c57c417be | 96 +++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 f4/dc2f3f4459d885c075db3a536ae05c57c417be diff --git a/f4/dc2f3f4459d885c075db3a536ae05c57c417be b/f4/dc2f3f4459d885c075db3a536ae05c57c417be new file mode 100644 index 000000000..5e2cd4070 --- /dev/null +++ b/f4/dc2f3f4459d885c075db3a536ae05c57c417be @@ -0,0 +1,96 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id EEA4D431FB6 + for ; Wed, 17 Apr 2013 01:55:59 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -2.299 +X-Spam-Level: +X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 + tests=[RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001] + autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id P3opQiz9qrxY for ; + Wed, 17 Apr 2013 01:55:59 -0700 (PDT) +Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) + (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 74917431FAF + for ; Wed, 17 Apr 2013 01:55:59 -0700 (PDT) +Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) + by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with + ESMTP id r3H8towA003507 + (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); + Wed, 17 Apr 2013 08:55:51 GMT +Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) + by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id + r3H8tmxI006343 + (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); + Wed, 17 Apr 2013 08:55:49 GMT +Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) + by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id + r3H8tlum003615; Wed, 17 Apr 2013 08:55:48 GMT +Received: from pub.cz.oracle.com (/10.163.101.122) + by default (Oracle Beehive Gateway v4.0) + with ESMTP ; Wed, 17 Apr 2013 01:55:47 -0700 +Date: Wed, 17 Apr 2013 10:53:54 +0200 +From: Vladimir Marek +To: Blake Jones +Subject: Re: crash during saving +Message-ID: <20130417085354.GE7807@pub.cz.oracle.com> +Mail-Followup-To: Blake Jones , notmuch@notmuchmail.org +References: <20130416135600.GA7807@pub.cz.oracle.com> + <13395.1366142328@foo.net> +MIME-Version: 1.0 +Content-Type: text/plain; charset=utf-8 +Content-Disposition: inline +In-Reply-To: <13395.1366142328@foo.net> +User-Agent: Mutt/1.5.21 (2010-09-15) +X-Source-IP: acsinet21.oracle.com [141.146.126.237] +Cc: notmuch@notmuchmail.org +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +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: Wed, 17 Apr 2013 08:56:00 -0000 + +> > I just indexed my mail archive by notmuch and I'm starting to play +> > with mutt-kz. The biggest stopper right now is that mutt cores when +> > set already read mail to new (toggle-new in mutt). Once I try to leave +> > the virtual folder (be it to another folder or because of quitting +> > mutt) it crashes. +> > +> > I haven't had the time yet to investigate deeper, so I'll just post +> > whatever info I have and hope that it will be something obvious for +> > you :) +> +> I saw something like that when I was first using mutt-kz as well... +> it ended up that I had compiled libxapian with one version of gcc (3.4.3 +> maybe?) and notmuch with 4.5.2, and the C++ runtime libraries were +> incompatible between the two versions. In my case, any time it tried to +> throw an exception (e.g. when I removed a tag that was not present) it +> would die with a similar stack trace. (And, of course, that was on +> Solaris :) ) + +Right, so the problem really seems to be in throwing/catching exception. +Function "_notmuch_message_remove_term" is supposed to catch the +exception and ignore it. Which does not happen in my case. + +On a side note, I wonder, is catching exception faster than going +through list of tags to see if given tag exists? Might be interesting to +compare. + +Cheers +-- + Vlad -- 2.26.2