Re: [Mutt] #2902: Segmentation fault with IMAP/"The message index

#2902: Segmentation fault with IMAP/"The message index is incorrect. Try reopening the mailbox." +--- Reporter: neteler| Owner: brendan Type: defect | Status: closed Priority: major |

Re: [Mutt] #2902: Segmentation fault with IMAP/"The message index

#2902: Segmentation fault with IMAP/"The message index is incorrect. Try reopening the mailbox." --+- Reporter: neteler | Owner: brendan Type: defect | Status: started Priority: major| Milest

Re: [Mutt] #2902: Segmentation fault with IMAP/"The message index

#2902: Segmentation fault with IMAP/"The message index is incorrect. Try reopening the mailbox." --+- Reporter: neteler | Owner: brendan Type: defect | Status: assigned Priority: major| Mile

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Changes (by neteler): * cc: [EMAIL PROTECTED] (added) -- Ticket URL:

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Comment (by neteler): The "The message index is incorrect. Try reopening the mailbox." freeze happens here: (gdb) bt #0 0x0037ba5b9a92 in __read_nocancel () from /lib64/tls/libc.so.6 #1 0x004741a1 in raw_socket_read (conn=0x651db0, buf=Varia

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Changes (by neteler): * version: 1.5.15 => 1.5.16 Comment: Also segfault confirmed...: {{{ Bounce message to Markus Neteler ? ([yes]/no): yesDetaching after fork from child process 7497. Sorting mailbox... Program received signal SIGSEGV, Segmentat

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Comment (by neteler): Forgot to mention that after this message {{{ The message index is incorrect. Try reopening the mailbox. }}} mutt is actually frozen. -- Ticket URL:

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Comment (by neteler): A first test with 1.5.16 gives following message after less than 5 minutes: {{{ The message index is incorrect. Try reopening the mailbox. }}} With CTRL-Z I can still get back to the command line and kill the mutt process :-( --

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Changes (by brendan): * status: new => assigned * milestone: => 1.6 Comment: Can you reproduce this with 1.5.16? -- Ticket URL:

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Comment (by neteler): ... and one more (last for today): {{{ Connecting to ntmail...[Thread debugging using libthread_db enabled] [New Thread 182894227392 (LWP 7578)] Fetching message headers... 1120/1123 Program received signal SIGSEGV, Segmentation fau

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Comment (by neteler): I run it again, and after less than one our it crashes with {{{ -*-Mutt: imap://[EMAIL PROTECTED]/INBOX [Msgs:1120 New:2 Old:153 Del:8 30M ]---(reverse-date-received/date)- Fetching message headers... 1740/1740 Program received sign

[Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP Mutt regularly crashes for me. I am using an IMAP box (Microsoft IMAP server), in parallel also thunderbird is listening to auto-filter selected messages into IMAP folders. This happens: {{{ ---Mutt: imap://[EMAIL PROTECTED]/INBOX [Msgs:1126 New:169 30M]-