#2935: Occasional segfault when IMAP inbox updates
---------------------+------------------------------------------------------
Reporter: skunk | Owner: brendan
Type: defect | Status: infoneeded
Priority: major | Milestone: 1.6
Component: IMAP | Version: 1.5.19
Resolution: | Keywords: duplicate 2902
---------------------+------------------------------------------------------
Changes (by brendan):
* status: started => infoneeded
Old description:
> Version: mutt-20070709[[BR]]
> Platform: Debian/etch on amd64
>
> I have an IMAP inbox that is updated asynchronously on a remote server.
> Sometimes, when new messages come in, and Mutt has uncommitted changes to
> the inbox, it segfaults.
>
> This is what it looks like in GDB:
>
> {{{
> Fetching message headers... 1899/1900
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000044f25e in mx_update_context (ctx=0x7b15d0, new_messages=4)
> at mx.c:1566
> 1566 h->security = crypt_query (h->content);
> (gdb) p h->content
> Cannot access memory at address 0x50
> (gdb)
> }}}
>
> I have two core dumps saved from these crashes, and so can return
> additional telemetry upon request.
New description:
Version: mutt-20070709[[BR]]
Platform: Debian/etch on amd64
I have an IMAP inbox that is updated asynchronously on a remote server.
Sometimes, when new messages come in, and Mutt has uncommitted changes to
the inbox, it segfaults.
This is what it looks like in GDB:
{{{
Fetching message headers... 1899/1900
Program received signal SIGSEGV, Segmentation fault.
0x000000000044f25e in mx_update_context (ctx=0x7b15d0, new_messages=4)
at mx.c:1566
1566 h->security = crypt_query (h->content);
(gdb) p h->content
Cannot access memory at address 0x50
(gdb)
}}}
I have two core dumps saved from these crashes, and so can return
additional telemetry upon request.
--
--
Ticket URL: <http://dev.mutt.org/trac/ticket/2935#comment:24>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
