Re: read after free in notmuch new

David Bremner writes: > Tomi Ollila writes: > >> To me it looks like replacing g_hash_table_insert() with >> g_hash_table_replace() would do the trick. >> >> (or even g_hash_table_add()!) >> >> One has to read the documentation a bit (and compare the

Re: bug report

Andy Wills writes: > > andy@andy-x200:~/work/talks/2017/icps$ notmuch new > Processed 230 total files in 7s (29 files/sec.). > Added 212 new messages to the database. Removed 85 messages. Detected 18 file > renames. > Error: A Xapian exception occurred flushing database:

Re: read after free in notmuch new

Tomi Ollila writes: > To me it looks like replacing g_hash_table_insert() with > g_hash_table_replace() would do the trick. > > (or even g_hash_table_add()!) > > One has to read the documentation a bit (and compare the docstrings of > these 2 functions to guess the missing

bug report

Hi, I've been consistently getting an error of this form: andy@andy-x200:~/work/talks/2017/icps$ notmuch new Processed 230 total files in 7s (29 files/sec.). Added 212 new messages to the database. Removed 85 messages. Detected 18 file renames. Error: A Xapian exception occurred flushing

Re: read after free in notmuch new

On Tue, Feb 21 2017, David Bremner wrote: > David Bremner writes: > >> David Bremner writes: >> >>> I haven't had a chance to really track this down, but it seems there is >>> a memory error in notmuch new (or a maybe false positive from

Re: notmuch version/Python bindings

Hi there, just tried to delete the notmuch packagr on pypi. While I am listed as the author, I do not own the package and it lists "Package Index Owner: Julian". It might be that I have already transferred the ownership of the package, but I don't remember who Julian is. Has anyone else a clue?

Re: Proposed fix for test failures due to long socket paths

David Bremner writes: > Amadeusz Żołnowski found a bug in the test suite that causes gpg > failures when the path of the test directory is sufficiently long. > His current solution in Gentoo is to move the sockets into /tmp. It > seems cleaner to enable gnupg's built in /run

Re: some issues with emacs 25

Matthew Lear writes: > Thanks David. Yes it does. After recompiling the v25 lisp with these > changes, I'm unable to reproduce the problems with both the test emails I > sent you. Wonderful :-) > Are you going to raise this with upstream? > Cheers, > Matt Yes, I've filed

Re: some issues with emacs 25

On 18 Feb 2017 01:01, "David Bremner" wrote: So I _finally_ got around to looking at these, and I think it's roughly the same shr bug as before but some different functions. I could actually only duplicate the bug with emacs-reply-fail-ec message, but that was fixed by the