Re: Segfault on notmuch compiled using commit 73cebe6e7233f59ba26d9f7c05265b7776795818

Subject: Re: Segfault on notmuch compiled using commit 73cebe6e7233f59ba26d9f7c05265b7776795818

Date: Tue, 28 May 2019 09:59:02 -0300

To: sebastien rey-coyrehourcq, Notmuch Mail

Cc:

From: David Bremner


sebastien rey-coyrehourcq <sebastien.rey-coyrehourcq@univ-rouen.fr>
writes:

> (gdb) backtrace
> #0  0x00007ffff6969410 in g_mime_stream_construct () at /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
> #1  0x00007ffff696d124 in g_mime_stream_fs_new_with_bounds () at /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
> #2  0x00007ffff7bc6f3f in g_mime_stream_gzfile_open (filename=<optimized out>) at util/gmime-extra.c:54
> #3  0x00007ffff7bb0b51 in _notmuch_message_file_open_ctx (notmuch=notmuch@entry=0x5555557b67d0, ctx=ctx@entry=0x0, filename=filename@entry=0x5555557eceb0 "/home/reyman/Mail/unthinkingdepths/0_InfoLabos/.mbsyncstate") at lib/message-file.c:73

1) What can you tell me about .mbsyncstate? Is it a dangling symlink?
An empty file? very large?

2) what happens if you add .mbsyncstate to new.ignore with 'notmuch config'?
_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Thread: