Mutt | 2 Jan 19:38 2010

Re: [Mutt] #3288: seg fault in mx_update_context

#3288: seg fault in mx_update_context
--------------------+-------------------------------------------------------
 Reporter:  prlw1   |       Owner:  brendan 
     Type:  defect  |      Status:  accepted
 Priority:  major   |   Milestone:          
Component:  IMAP    |     Version:  1.5.20  
 Keywords:  patch   |  
--------------------+-------------------------------------------------------

Comment(by prlw1):

 I have just had exactly this same core dump with today's mutt head.

 {{{
 % hg parent
 changeset:   6035:31881f38ca1e
 branch:      HEAD
 tag:         tip
 user:        Brendan Cully <brendan <at> kublai.com>
 date:        Tue Dec 29 00:33:20 2009 -0500
 summary:     Hack mutt_wstr_trunc to treat M_TREE characters as 1 cell.
 }}}

 {{{
 Program terminated with signal 11, Segmentation fault.
 #0  0x08081f4f in mx_update_context (ctx=0xbb719680, new_messages=235037)
     at mx.c:1544
 1544          h->virtual = ctx->vcount++;
 (gdb) bt
 #0  0x08081f4f in mx_update_context (ctx=0xbb719680, new_messages=235037)
(Continue reading)

Mutt | 5 Jan 16:33 2010

Re: [Mutt] #3288: seg fault in mx_update_context

#3288: seg fault in mx_update_context
--------------------+-------------------------------------------------------
 Reporter:  prlw1   |       Owner:  brendan 
     Type:  defect  |      Status:  accepted
 Priority:  major   |   Milestone:          
Component:  IMAP    |     Version:  1.5.20  
 Keywords:  patch   |  
--------------------+-------------------------------------------------------

Comment(by prlw1):

 Having just had a good look through similar closed tickets, I should add
 that I am not using the header cache.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3288#comment:9>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Mutt | 5 Jan 16:55 2010

Re: [Mutt] #3288: seg fault in mx_update_context

#3288: seg fault in mx_update_context
--------------------+-------------------------------------------------------
 Reporter:  prlw1   |       Owner:  brendan 
     Type:  defect  |      Status:  accepted
 Priority:  major   |   Milestone:          
Component:  IMAP    |     Version:  1.5.20  
 Keywords:  patch   |  
--------------------+-------------------------------------------------------

Comment(by prlw1):

 I should also add that

 {{{
 (gdb) print *ctx
 $5 = {path = 0xbb795ba0 "imap://localhost/INBOX", fp = 0x0, mtime = 0,
   size = 3062720723, vsize = 0, pattern = 0x0, limit_pattern = 0x0,
   hdrs = 0xbb301000, last_tag = 0x0, tree = 0x0, id_hash = 0x0,
   subj_hash = 0x0, thread_hash = 0x0, v2r = 0xbb201000, hdrmax = 235063,
   msgcount = 235037, vcount = 234938, tagged = 0, new = 219, unread =
 234851,
   deleted = 0, flagged = 0, msgnotreadyet = -1, magic = 5, rights = "�\a",
   locked = 0, changed = 0, readonly = 0, dontwrite = 0, append = 0, quiet
 = 0,
   collapsed = 0, closing = 0, data = 0xbb7670c0,
   mx_close = 0x80b8920 <imap_close_mailbox>}
 }}}

 i.e., ctx->msgcount = 235037 > msgno = 234938, so it isn't the red herring
 that ctx->hdrs[msgcount] should be NULL.
(Continue reading)

Mutt | 5 Jan 17:41 2010

Re: [Mutt] #3288: seg fault in mx_update_context

#3288: seg fault in mx_update_context
--------------------+-------------------------------------------------------
 Reporter:  prlw1   |       Owner:  brendan 
     Type:  defect  |      Status:  accepted
 Priority:  major   |   Milestone:          
Component:  IMAP    |     Version:  1.5.20  
 Keywords:  patch   |  
--------------------+-------------------------------------------------------

Comment(by prlw1):

 Ah:

 {{{
 [2010-01-05 16:12:40] Fetching message headers... 0/235043 (0%)
 [2010-01-05 16:12:40] 4> a0005 FETCH 1:235043 (UID FLAGS INTERNALDATE
 RFC822.SIZ
 E BODY.PEEK[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES
 CONTENT
 -TYPE CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES LIST-POST
 X-LABEL)])^M
 }}}
 ...

 {{{
 [2010-01-05 16:26:32] 4< * 234938 FETCH (FLAGS () UID 735278 INTERNALDATE
 " 2-Ja
 n-2010 16:16:37 +0000" RFC822.SIZE 9007 BODY[HEADER.FIELDS (DATE FROM
 SUBJECT TO
  CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-REPLY-TO
(Continue reading)

Mutt | 5 Jan 18:13 2010

Re: [Mutt] #3288: seg fault in mx_update_context

#3288: seg fault in mx_update_context
--------------------+-------------------------------------------------------
 Reporter:  prlw1   |       Owner:  brendan 
     Type:  defect  |      Status:  accepted
 Priority:  major   |   Milestone:          
Component:  IMAP    |     Version:  1.5.20  
 Keywords:  patch   |  
--------------------+-------------------------------------------------------

Comment(by prlw1):

 {{{
 . fetch 234939 (body[text])
 * 234939 FETCH (FLAGS (\Seen) BODY[TEXT] NIL)
 . OK Completed (0.000 sec)
 }}}

 So now there are 2 issues: mutt ought not to coredump if receives that
 response from a server. A non-mutt issue is why what looks like a decent
 message on disk is causing the server to say it has no body...

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3288#comment:12>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Mutt | 6 Jan 13:26 2010

Re: [Mutt] #3288: seg fault in mx_update_context

#3288: seg fault in mx_update_context
--------------------+-------------------------------------------------------
 Reporter:  prlw1   |       Owner:  brendan 
     Type:  defect  |      Status:  accepted
 Priority:  major   |   Milestone:          
Component:  IMAP    |     Version:  1.5.20  
 Keywords:  patch   |  
--------------------+-------------------------------------------------------

Comment(by prlw1):

 So this has turned into #3316

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3288#comment:13>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Mutt | 6 Jan 13:43 2010

Re: [Mutt] #3288: seg fault in mx_update_context

#3288: seg fault in mx_update_context
--------------------+-------------------------------------------------------
 Reporter:  prlw1   |       Owner:  brendan 
     Type:  defect  |      Status:  accepted
 Priority:  major   |   Milestone:          
Component:  IMAP    |     Version:  1.5.20  
 Keywords:  patch   |  
--------------------+-------------------------------------------------------

Comment(by prlw1):

 Reconstructing the cyrus mailbox means it no longer tells mutt that the
 troublesome message's body is empty. So, what should mutt do? Rather than
 "ignore message", scream "your mailbox is corrupt!" ? (Then the headers
 shouldn't end up being NULL)

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3288#comment:14>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Mutt | 9 Jan 14:00 2010

Re: [Mutt] #3318: Attachments not shown if mail is pgp/mime encrypted

#3318: Attachments not shown if mail is pgp/mime encrypted
----------------------------+-----------------------------------------------
 Reporter:  tannhauser      |       Owner:  mutt-dev
     Type:  defect          |      Status:  new     
 Priority:  major           |   Milestone:          
Component:  mutt            |     Version:  1.5.20  
 Keywords:  pgp attachment  |  
----------------------------+-----------------------------------------------

Comment(by longlivedeath):

 Happens to me too with mutt 1.5.20 on Ubuntu 9.10. I can't see attachments
 sent by Thunderbird/Enigmail users.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3318#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Mutt | 9 Jan 14:03 2010

Re: [Mutt] #3318: Attachments not shown if mail is pgp/mime encrypted

#3318: Attachments not shown if mail is pgp/mime encrypted
----------------------------+-----------------------------------------------
 Reporter:  tannhauser      |       Owner:  mutt-dev
     Type:  defect          |      Status:  new     
 Priority:  major           |   Milestone:          
Component:  mutt            |     Version:  1.5.20  
 Keywords:  pgp attachment  |  
----------------------------+-----------------------------------------------
Changes (by longlivedeath):

 * cc: the.dead.shall.rise <at> … (added)

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3318#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Mutt | 10 Jan 20:57 2010

Re: [Mutt] #3316: mutt hangs when some IMAP FETCH responses were ignored

#3316: mutt hangs when some IMAP FETCH responses were ignored
----------------------+-----------------------------------------------------
 Reporter:  mlichvar  |       Owner:  brendan
     Type:  defect    |      Status:  new    
 Priority:  major     |   Milestone:         
Component:  IMAP      |     Version:         
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by raorn):

 * cc: raorn (added)

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3316#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent


Gmane