On Mon, Sep 12, 2016 at 04:51:21PM +0200, Sebastian Ramacher wrote: > Package: mutt > Version: 1.7.0-3 > Severity: normal > > Since the last update, I repeatedly get SIGSEGVs while going through some > unseen > mails in my inbox: > > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x000055596b73f69a in update_index (menu=0x0, ctx=0x55596d883090, > check=1, oldcount=26756, index_hint=0) at ../../curs_main.c:371 > 371 ../../curs_main.c: No such file or directory. > (gdb) bt > #0 0x000055596b73f69a in update_index (menu=0x0, ctx=0x55596d883090, > check=1, oldcount=26756, index_hint=0) at ../../curs_main.c:371 > #1 0x000055596b772e7d in mutt_pager (banner=banner@entry=0x0, > fname=fname@entry=0x7ffc75f98e70 > "/tmp/mutt-jupiter-1000-22076-6547043317620087410", flags=<optimized out>, > flags@entry=66, extra=extra@entry=0x7ffc75f98e40) at ../../pager.c:2031 > #2 0x000055596b734045 in mutt_display_message (cur=0x55596f740ed0) at > ../../commands.c:225 > #3 0x000055596b74464b in mutt_index_menu () at ../../curs_main.c:1902 > #4 0x000055596b7247aa in main (argc=1, argv=<optimized out>) at > ../../main.c:877 >
I believe this has been solved in 1.8.3+neomutt20170609-1; I've removed all pager.c patches and we moved to neomutt upstream. Could you tell me if this is still happening for you?
