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 AECFD431FD0 for ; Fri, 30 Sep 2011 06:12:59 -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 HJ4qHegfL6hA for ; Fri, 30 Sep 2011 06:12:59 -0700 (PDT) Received: from socrates.hocat.ca (socrates.hocat.ca [76.10.188.53]) by olra.theworths.org (Postfix) with ESMTP id 01BD0431FB6 for ; Fri, 30 Sep 2011 06:12:58 -0700 (PDT) Received: from hermes.hocat.ca (hermes.hocat.ca [69.165.170.253]) by socrates.hocat.ca (Postfix) with SMTP id 71F752485; Fri, 30 Sep 2011 07:12:56 -0600 (MDT) Received: (nullmailer pid 23112 invoked by uid 1000); Fri, 30 Sep 2011 13:12:50 -0000 From: Tom Prince To: Justus Winter <4winter@informatik.uni-hamburg.de>, notmuch@notmuchmail.org Subject: Re: python(?): process died while iterating over Messages object In-Reply-To: References: User-Agent: Notmuch/0.7 (http://notmuchmail.org) Emacs/23.3.3 (x86_64-pc-linux-gnu) Date: Fri, 30 Sep 2011 09:12:50 -0400 Message-ID: <877h4q9nsd.fsf@hermes.hocat.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Fri, 30 Sep 2011 13:12:59 -0000 On Fri, 30 Sep 2011 12:43:53 +0200, Justus Winter <4winter@informatik.uni-hamburg.de> wrote: > while iterating over a query result set my process died with > > > terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' > > Aborted > > I am not sure where this came from, grepping throuth notmuchs soure > didn't reveal the location. So this might be not specific to the > python bindings at all. std::terminate is called when an exception is thrown in C++, and there are no enclosing try blocks that will catch the exception. Tom