[MacPorts] #43697: mutt-devel in ports still segfaults in mx_update_context

MacPorts noreply at macports.org
Tue May 13 11:34:28 PDT 2014


#43697: mutt-devel in ports still segfaults in mx_update_context
-------------------------+--------------------------------
  Reporter:  paul.jan@…  |      Owner:  macports-tickets@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.2.1
Resolution:              |   Keywords:
      Port:  mutt-devel  |
-------------------------+--------------------------------

Old description:

> Hi,
>
> seems like mutt-devel in ports is still suffering from mx_update_context
> segfault while accessing IMAP folders:
>
> Process 30678 stopped
> * thread #1: tid = 0x99b263, 0x000000010003c5f7 mutt`mx_update_context +
> 50, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
> (code=1, address=0x50)
>     frame #0: 0x000000010003c5f7 mutt`mx_update_context + 50
> mutt`mx_update_context + 50:
> -> 0x10003c5f7:  movq   0x50(%rbx), %rdi
>    0x10003c5fb:  callq  0x10000c8f6               ; crypt_query
>    0x10003c600:  andl   $0x7ff, %eax
>    0x10003c605:  movl   (%rbx), %ecx
> (lldb) thread backtrace
> * thread #1: tid = 0x99b263, 0x000000010003c5f7 mutt`mx_update_context +
> 50, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
> (code=1, address=0x50)
>   * frame #0: 0x000000010003c5f7 mutt`mx_update_context + 50
>     frame #1: 0x000000010008222d mutt`imap_read_headers + 1854
>     frame #2: 0x000000010007f894 mutt`imap_open_mailbox + 1318
>     frame #3: 0x000000010003aa47 mutt`mx_open_mailbox + 941
>     frame #4: 0x0000000100031efb mutt`main + 4881
>
> the issue seems to be related to:
>
> http://dev.mutt.org/trac/ticket/3288
>
> was this fix pulled into this port?

New description:

 Hi,

 seems like mutt-devel in ports is still suffering from mx_update_context
 segfault while accessing IMAP folders:

 {{{
 Process 30678 stopped
 * thread #1: tid = 0x99b263, 0x000000010003c5f7 mutt`mx_update_context +
 50, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1,
 address=0x50)
     frame #0: 0x000000010003c5f7 mutt`mx_update_context + 50
 mutt`mx_update_context + 50:
 -> 0x10003c5f7:  movq   0x50(%rbx), %rdi
    0x10003c5fb:  callq  0x10000c8f6               ; crypt_query
    0x10003c600:  andl   $0x7ff, %eax
    0x10003c605:  movl   (%rbx), %ecx
 (lldb) thread backtrace
 * thread #1: tid = 0x99b263, 0x000000010003c5f7 mutt`mx_update_context +
 50, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1,
 address=0x50)
   * frame #0: 0x000000010003c5f7 mutt`mx_update_context + 50
     frame #1: 0x000000010008222d mutt`imap_read_headers + 1854
     frame #2: 0x000000010007f894 mutt`imap_open_mailbox + 1318
     frame #3: 0x000000010003aa47 mutt`mx_open_mailbox + 941
     frame #4: 0x0000000100031efb mutt`main + 4881
 }}}

 the issue seems to be related to:

 http://dev.mutt.org/trac/ticket/3288

 was this fix pulled into this port?

--

Comment (by ryandesign@…):

 > was this fix pulled into this port?

 I don't think so.

 I guess we should update mutt-devel to 1.5.23 which presumably will
 include this fix.

-- 
Ticket URL: <https://trac.macports.org/ticket/43697#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list