Ralph Seichter <ab...@monksofcool.net> writes: > While it is understood that Notmuch cannot write to the specified output > file, I don't think this should result in something as harsh as SIGABRT.
I agree it's a bit ugly to look at. At least it prints what the actual problem is before the abort. The abort seems to be generated from gzclose_w, so I guess it might just be an error handling bug in libz. Do you see any database corruption or more serious issues? d _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
