From: Blake Jones <blakej@foo.net>
To: Vladimir Marek <Vladimir.Marek@Oracle.COM>
Cc: notmuch@notmuchmail.org
Subject: Re: crash during saving
Date: Wed, 17 Apr 2013 07:05:29 -0700 [thread overview]
Message-ID: <20041.1366207529@foo.net> (raw)
In-Reply-To: Your message of "Wed, 17 Apr 2013 10:53:54 +0200." <20130417085354.GE7807@pub.cz.oracle.com>
> 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.
Yep, that was exactly what I was seeing.
> 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.
I tried that as a workaround at first (just to get it working, not
caring about performance). But I realized that libxapian uses
exceptions for a lot of failure modes, and I actually ran into one or
two others, so I decided I needed to just get it working.
To simplify the problem, you might want to try building a very simple
stub version of the whole thing -- i.e. a C program that makes a call to
a C-interface "liba", which just makes a call into a C++ "libb" library
and tries to catch an exception from it; the "libb" library would just
throw an exception. If that reproduces the problem, that might help you
debug your setup.
(Again, I eventually settled on using GCC 4.5.2, and didn't have the
intestinal fortitude to get Studio working. Especially once I saw
problems with C++ exception handling. If you can get it working, more
power to you!)
Blake
next prev parent reply other threads:[~2013-04-17 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 13:56 crash during saving Vladimir Marek
2013-04-16 19:58 ` Blake Jones
2013-04-16 20:05 ` Vladimir Marek
2013-04-17 8:53 ` Vladimir Marek
2013-04-17 14:05 ` Blake Jones [this message]
2013-04-19 14:27 ` Vladimir Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041.1366207529@foo.net \
--to=blakej@foo.net \
--cc=Vladimir.Marek@Oracle.COM \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).