similar to: 2.2.19 crash

Hi All, I also tried with 16ff395c156e and 3d576d682137 patches that touch lib-storage/notify and still 2.2.19 cores: Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x0043bb8c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfdb34a0) at mailbox-list-notify.c:28 28 return notify->list->v.notify_next(notify, rec_r); (gdb)

On 10/29/2015 03:01 PM, Toni Mattila wrote: > Hi All, > > I also tried with 16ff395c156e and 3d576d682137 patches that touch > lib-storage/notify and still 2.2.19 cores: > > Core was generated by `dovecot/imap'. > Program terminated with signal 11, Segmentation fault. > #0 0x0043bb8c in mailbox_list_notify_next (notify=0x0, > rec_r=0xbfdb34a0) at

I've been seeing lots of index cache file errors (using mbox on Solaris 8 sparc 64-bit, but with 32-bit Dovecot) since I switched my account to Dovecot 1.2.0 (we're still on 1.0.15 mostly, but I'm hoping to upgrade to 1.1.17+ this summer, or 1.2.x if it's stable enough). e.g. Error: Corrupted index cache file <path>/.imap/INBOX/dovecot.index.cache: field index too large (47

For quite some time I have seen dovecot imap exit with a sig11 without any other error message, but usually with the frequency of between once per week and once per day (per server). A few weeks ago I finally enabled core dumping with debug symbols and it seemed to happen less often. I finally caught a coredump that wasn't overwritten. I have no idea what on the client end may cause it,

The following series flushes my documentation queue and replaces previous postings of those patches. The main difference is that the xl cfg file is now formatted using POD instead of markdown and presented as a manpage. I have setup a cron job to build docs/html and publish it at http://xenbits.xen.org/docs/unstable/ (it''s a bit bare right now). The motivation for some of these patches