Date: Tue, 16 Apr 2013 22:05:00 +0200
From: Vladimir Marek <Vladimir.Marek@Oracle.COM>
To: Blake Jones <blakej@foo.net>
Subject: Re: crash during saving
Message-ID: <20130416200500.GC7807@pub.cz.oracle.com>
Mail-Followup-To: Blake Jones <blakej@foo.net>, 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)
Cc: notmuch@notmuchmail.org
Precedence: list

> > 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 :) )

Hmm, I tried to be extra cautions to compile everything with stlport4,
but I'll double check that!

Thank you
-- 
	Vlad