From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id A285A431FB6 for ; Tue, 16 Apr 2013 12:58:50 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 iBj2s+j-AzlB for ; Tue, 16 Apr 2013 12:58:50 -0700 (PDT) Received: from foo.net (70-36-235-136.dsl.static.sonic.net [70.36.235.136]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 0BF31431FAF for ; Tue, 16 Apr 2013 12:58:49 -0700 (PDT) Received: from foo.net (localhost [127.0.0.1]) by foo.net (8.14.5+Sun/8.14.5) with ESMTP id r3GJwmvA013396; Tue, 16 Apr 2013 12:58:48 -0700 (PDT) To: Vladimir Marek Subject: =?UTF-8?B?UmU6IGNyYXNoIGR1cmluZyBzYXZpbmcg?= In-Reply-To: Your message of "Tue, 16 Apr 2013 15:56:00 +0200." <20130416135600.GA7807@pub.cz.oracle.com> Date: Tue, 16 Apr 2013 12:58:48 -0700 Message-ID: <13395.1366142328@foo.net> From: Blake Jones X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (foo.net [127.0.0.1]); Tue, 16 Apr 2013 12:58:48 -0700 (PDT) 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: Tue, 16 Apr 2013 19:58:50 -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 :) ) Blake