Re: [Mutt] #3004: Mutt 1.5.17 segfaults on debian etch
#3004: Mutt 1.5.17 segfaults on debian etch
---------------------+------------------------------------------------------
Reporter: vegard | Owner: brendan
Type: defect | Status: reopened
Priority: major | Milestone: 1.6
Component: IMAP | Version: 1.5.18
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment(by vegard):
Sorry, it's still crashing. Note that it only happens when I have other
e-mail clients (TB/Evolution) accessing the same mailbox simultaneously.
It never happens (as far as I can remember) when Mutt is alone. It usually
crashes when:
a) I'm starting Mutt, it has to open a lot (currently >70k) of messages,
and new messages are injected to the mailbox while Mutt is opening it.
b) I'm reading a message, and while I'm reading, new messages arrive in
the mailbox. I press 'i' to go back to the message index. Crash.
{{{
warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at
ffffe0b4
Core was generated by `mutt'.
Program terminated with signal 11, Segmentation fault.
#0 mx_update_context (ctx=0x812d810, new_messages=72374) at mx.c:1564
1564 h->security = crypt_query (h->content);
(gdb) bt
#0 mx_update_context (ctx=0x812d810, new_messages=72374) at mx.c:1564
#1 0x080ce22c in imap_read_headers (idata=0x8102398, msgbegin=0,
msgend=72372) at message.c:347
#2 0x080cbce9 in imap_open_mailbox (ctx=0x812d810) at imap.c:751
#3 0x08088a95 in mx_open_mailbox (path=0xfff3ae50
"imap://vegard@xxxxxxxxx:144/INBOX",
flags=<value optimized out>, pctx=0x11ab5) at mx.c:692
#4 0x080654ef in mutt_index_menu () at curs_main.c:1138
#5 0x0807e5ce in main (argc=Cannot access memory at address 0x46ad4
) at main.c:1019
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3004#comment:10>
Mutt <http://www.mutt.org/>
The Mutt mail user agent