Content-Type: multipart/mixed; boundary="===============0218522329202042320=="
MIME-Version: 1.0
In-Reply-To: <877h4q9nsd.fsf@hermes.hocat.ca>
References: <E1R9aZN-0005J0-U2@thinkbox.jade-hamburg.de>
	<877h4q9nsd.fsf@hermes.hocat.ca>
Subject: Re: python(?): process died while iterating over Messages object
To: Tom Prince <tom.prince@ualberta.net>, notmuch@notmuchmail.org
From: Justus Winter <4winter@informatik.uni-hamburg.de>
Date: Fri, 30 Sep 2011 15:40:29 +0200
Message-Id: <E1R9dKH-0003r5-9q@thinkbox.jade-hamburg.de>
Precedence: list

--===============0218522329202042320==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Quoting Tom Prince (2011-09-30 15:12:50)
>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::DatabaseModifi=
edError'
>> > 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.

Ah, so it is not specific to the python binding and it has to be
caught somewhere in the notmuch library, right?

I tried to locate the appropriate location but I'm afraid I got
lost. Could someone else take a look at this?

Thanks,
Justus
--===============0218522329202042320==
Content-Type: application/octet-stream
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=".signature"

bG92ZSB1IGFsb3QgQCxACgo=

--===============0218522329202042320==--