Yes, this is a pesky bug that I don't think we've quite tracked down yet. Looks like it's related to new messages getting announced when mutt isn't ready -- maybe when mutt is already in the process of parsing previously-announced new mail.
On Saturday, 07 June 2008 at 15:33, Jukka Salmi wrote: > Hello, > > some days ago Mutt crashed as follows: > > $ gdb /usr/local/bin/mutt mutt.core > GNU gdb 6.5 > [...] > Core was generated by `mutt'. > Program terminated with signal 11, Segmentation fault. > #0 0x080807f7 in mx_update_context (ctx=0xbb629380, new_messages=6) at > mx.c:1561 > 1561 h->security = crypt_query (h->content); > (gdb) bt > #0 0x080807f7 in mx_update_context (ctx=0xbb629380, new_messages=6) at > mx.c:1561 > #1 0x080c7cf3 in imap_read_headers (idata=0xbb6c20f0, msgbegin=31, > msgend=31) at message.c:346 > #2 0x080c0beb in imap_cmd_finish (idata=0xbb6c20f0) at command.c:308 > #3 0x080c2ae5 in imap_check_mailbox (ctx=0xbb629380, index_hint=0xbfbfdd30, > force=0) at imap.c:13 > #4 0x0805f9bd in mutt_index_menu () at curs_main.c:485 > #5 0x08078388 in main (argc=2, argv=0xbfbfea74) at main.c:999 > (gdb) > > Not sure what caused this crash, and thus I can't reproduce it. Any > hints? Core file is still available, in case this helps... > > > Regards, Jukka > > -- > bashian roulette: > $ ((RANDOM%6)) || rm -rf ~
