mutt-org crashed with SIGSEGV

[Matt Zimmerman]

Happened while switching IMAP folders. May be a duplicate of bug 666286

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: mutt 1.5.21-5
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 27 17:00:19 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/mutt-org
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: mutt
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
 PATH=(custom, user)
 LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x448a5b: mov 0x50(%rbx),%rdi
 PC (0x00448a5b) ok
 source "0x50(%rbx)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mutt
Stacktrace:
 #0 0x0000000000448a5b in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7ffff0b627f8
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 2965):
 #0 0x0000000000448a5b in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7ffff0b627f8
Title: mutt-org crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (25 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Stacktrace:
 #0 mx_update_context (ctx=0x1cb2c80, new_messages=<optimized out>) at ../mx.c:1650
         h = <error reading variable h (Cannot access memory at address 0x4d2c968)>
         msgno = 29
 Cannot access memory at address 0x7ffff0b627f8
StacktraceTop: mx_update_context (ctx=0x1cb2c80, new_messages=<optimized out>) at ../mx.c:1650

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[giaco (francesco-giacomini)]

This is the stacktrace for mutt compiled without optimization. Apart from that, it's the version coming with oneiric.

Core was generated by `mutt'.
Program terminated with signal 11, Segmentation fault.
#0 0x000000000045f1e0 in mx_update_context (ctx=0x1003f00, new_messages=30) at ../mx.c:1650
1650 h->security = crypt_query (h->content);
(gdb) bt
#0 0x000000000045f1e0 in mx_update_context (ctx=0x1003f00, new_messages=30) at ../mx.c:1650
#1 0x00000000004da097 in imap_read_headers (idata=0x1005ec0, msgbegin=0, msgend=30)
    at ../../imap/message.c:386
#2 0x00000000004d51f2 in imap_open_mailbox (ctx=0x1003f00) at ../../imap/imap.c:756

In my case mutt fails almost systematically on a small inbox.

One suspicious message in .muttdebug0 is:

[...] bad cache entry at 0, giving up

which probably causes some "holes" in the ctd->hdrs array, which subsequently are not properly managed.

[giaco (francesco-giacomini)]

mutt-1.5.21 coming from mutt.org doesn't crash.

[Robie Basak (racb)]

Full backtrace attached in case it helps. Some sensitive information replaced with Xs. This happens every few days for me. I think it began when I upgraded to Oneiric.

[dino99 (9d9)]

This version has expired long time ago, and is no more supported