Opened 10 years ago
Last modified 7 years ago
#43697 closed defect
mutt-devel in ports still segfaults in mx_update_context — at Initial Version
Reported by: | paul.jan@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | ||
Port: | mutt-devel |
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)
the issue seems to be related to:
http://dev.mutt.org/trac/ticket/3288
was this fix pulled into this port?
Note: See
TracTickets for help on using
tickets.