Your message dated Sun, 15 Mar 2009 11:31:18 +0000
with message-id <[email protected]>
and subject line mutt: Mutt occasionally gets SIGSEGV on IMAP mailbox check
has caused the Debian Bug report #438592,
regarding mutt: Mutt occasionally gets SIGSEGV on IMAP mailbox check
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
438592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438592
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 1.5.16-3
Severity: normal


>From time to time, mutt will crash with a SIGSEGV when doing an IMAP 
mailbox check.  I build an unstripped version of the package with 
debugging symbols enabled to get better data.

Here's the backtrace:

(gdb) where
#0  mx_update_context (ctx=0x770130, new_messages=1) at ../mx.c:1669
#1  0x000000000048dd3d in imap_read_headers (idata=0x76fad0, msgbegin=35182, 
msgend=35182) at ../../imap/message.c:346
#2  0x0000000000486423 in imap_cmd_finish (idata=0x76fad0) at 
../../imap/command.c:308
#3  0x00000000004868fb in imap_cmd_step (idata=0x76fad0) at 
../../imap/command.c:213
#4  0x000000000048796a in imap_exec (idata=0x76fad0, cmdstr=<value optimized 
out>, flags=0) at ../../imap/command.c:262
#5  0x000000000048849f in imap_check_mailbox (ctx=<value optimized out>, 
index_hint=<value optimized out>, force=0) at ../../imap/imap.c:1385
#6  0x000000000041c12d in mutt_index_menu () at ../curs_main.c:498
#7  0x000000000043736a in main (argc=1, argv=0x7fff562fb778) at ../main.c:995


The bit of code is here (line 1669):

1664        h = ctx->hdrs[msgno];
1665
1666        if (WithCrypto)
1667        {
1668          /* NOTE: this _must_ be done before the check for mailcap! */
1669          h->security = crypt_query (h->content);
1670        }
1671
1672        if (!ctx->pattern)
1673        {

h in this case is NULL (hence the SIGSEGV), as is ctx->hdrs[msgno].  
msgno in this specific crash is 35182.  ctx->msgcount is 35183.  So this 
is the last message.

ctx->hdrs[msgno-1] points to something real.  This may end up being a 
fencepost bug to me but I don't know enough about the mutt internals to 
say where it is just yet.


I can't reproduce this at will but it occurs with some frequency (once 
every couple of days or so with the mailbox I'm using).  Mutt is talking 
to dbmail (2.2.5-1) on the backend.


I've saved the core file just in case you need me to go back and look at 
this.



-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.20-1-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mutt depends on:
ii  libc6                    2.6-2           GNU C Library: Shared libraries
ii  libgdbm3                 1.8.3-3         GNU dbm database routines (runtime
ii  libgnutls13              1.6.3-1         the GNU TLS library - runtime libr
ii  libidn11                 0.6.5-1         GNU libidn library, implementation
ii  libncursesw5             5.6+20070716-1  Shared libraries for terminal hand
ii  libsasl2-2               2.1.22.dfsg1-13 Authentication abstraction library

Versions of packages mutt recommends:
ii  locales                       2.6-2      GNU C Library: National Language (
ii  mime-support                  3.39-1     MIME files 'mime.types' & 'mailcap
ii  postfix [mail-transport-agent 2.4.3-1    High-performance mail transport ag

-- no debconf information


--- End Message ---
--- Begin Message ---
Hi,
I'm closing the bug because no information was provided, I hope
my last correspondence solves your problem.

If you are still having problems please feel free to reopen
the bug.

Cheers
Antonio


--- End Message ---

Reply via email to