a0640a0532
The core dump only seems to occur if mu4e-headers-include-related is set to t. Apparently, std::string's c_str() method is confusing to many people, c.f. http://stackoverflow.com/questions/22330250/how-to-return-a-stdstring-c-str The answer seems to be that the pointer c_str() returns may not be valid past the current statement; returning it, or even using it subsequently can have you sending a wild pointer into e.g. g_strdup(). In short, it seems idioms like this are okay: return g_strcmp0 (s1.c_str(), s2.c_str()) < 0; Whereas idioms like this are not: const char *msgid (iter->msgid().c_str()); return msgid ? g_strdup (msgid) : NULL; At least in my environment by the time we get to g_strdup() the pointer returned by c_str() is wild and points at garbage. Since g_strdup() returns NULL if passed NULL, it seems collapsing it into a single line is not only possible but necessary. I've looked at all of the calls to c_str() in mu and it appears to me this was the one remaining one that was bad.
README
======
Welcome to mu!
---------------
Given the enormous amounts of e-mail many people gather and the importance of
e-mail message in our work-flows, it's essential to quickly deal with all that
mail - in particular, to instantly find that one important e-mail you need right
now.
[mu] is a tool for dealing with e-mail messages stored in the
Maildir-format. =mu='s purpose in life is to help you to quickly find the
messages you need; in addition, it allows you to view messages, extract
attachments, create new maildirs, and so on. See the [mu cheatsheet] for some
examples. =mu= is fully documented.
After indexing your messages into a [Xapian]-database, you can search them using
a custom query language. You can use various message fields or words in the
body text to find the right messages.
Built on top of the mu, are some extensions (included in this package):
- mu-for-emacs ([mu4e]): a full-featured e-mail client that runs inside emacs
- [mu-guile]: bindings for the Guile/Scheme programming language (version 2.0
and later)
- a toy GTK+-interface called 'mug' (in the 'toys/' subdir)
=mu= is written in C and a bit of C++ (to interface with Xapian), with =mu4e=
written in [Emacs-Lisp] and =mu-guile= in a mix of C and Scheme.
Note, =mu= is available in Debian/Ubuntu under the name =maildir-utils=;
apparently because they don't like short name. It's also possible to confuse
that name with the [GNU Mailutils] project (which is totally unrelated) - but
now you have been warned.
[mu]: http://www.djcbsoftware.nl/code/mu
[mu cheatsheet]: http://www.djcbsoftware.nl/code/mu/cheatsheet.html
[Xapian]: http://www.xapian.org
[mu4e]: http://www.djcbsoftware.nl/code/mu/mu4e.html
[mu-guile]: http://www.djcbsoftware.nl/code/mu/mu-guile.html
[Emacs-Lisp]: http://en.wikipedia.org/wiki/Emacs-Lisp
[GNU Mailutils]: http://mailutils.org/