I've been having some trouble with imaps and mutt when trying
to talk to remote mailboxes. In using mutt-1.5.23 the problem appears
to be somewhere in the mutt_socket_readchar cache/optimization.
This occurs both with OpenSSL and GNUTLS and the backtraces
look similar to this:
(gdb) bt
#0 0x00007fb6f066fdad in recv () from /lib64/libc.so.6
#1 0x00007fb6f1265cd6 in _gnutls_io_read_buffered ()
from /lib64/libgnutls.so.28
#2 0x00007fb6f126073c in _gnutls_recv_in_buffers ()
from /lib64/libgnutls.so.28
#3 0x00007fb6f12620c8 in _gnutls_recv_int () from /lib64/libgnutls.so.28
#4 0x00007fb6f12625d4 in gnutls_record_recv () from /lib64/libgnutls.so.28
#5 0x0000000000491fbf in tls_socket_read ()
#6 0x0000000000491455 in mutt_socket_readchar ()
#7 0x000000000049159d in mutt_socket_readln_d ()
#8 0x00000000004993f9 in imap_cmd_step ()
#9 0x00000000004a109c in imap_fetch_message ()
#10 0x000000000044535d in mx_open_message ()
#11 0x00000000004506b7 in msg_search ()
#12 0x00000000004520c4 in mutt_pattern_exec ()
#13 0x000000000042550d in mutt_set_header_color ()
#14 0x000000000042555f in index_color ()
#15 0x000000000043d415 in menu_redraw_index ()
#16 0x000000000041f6a5 in mutt_index_menu ()
#17 0x0000000000408ad7 in main ()
or
(gdb) bt
#0 0x00007f32244e6dad in recv () from /lib64/libc.so.6
#1 0x00007f32250dccd6 in _gnutls_io_read_buffered ()
from /lib64/libgnutls.so.28
#2 0x00007f32250d773c in _gnutls_recv_in_buffers ()
from /lib64/libgnutls.so.28
#3 0x00007f32250d90c8 in _gnutls_recv_int () from /lib64/libgnutls.so.28
#4 0x00007f32250d95d4 in gnutls_record_recv () from /lib64/libgnutls.so.28
#5 0x0000000000491fbf in tls_socket_read ()
#6 0x0000000000491455 in mutt_socket_readchar ()
#7 0x000000000049159d in mutt_socket_readln_d ()
#8 0x00000000004993f9 in imap_cmd_step ()
#9 0x000000000049a758 in imap_exec ()
#10 0x000000000049ca50 in imap_check_mailbox ()
#11 0x0000000000445275 in mx_check_mailbox ()
#12 0x000000000041ef20 in mutt_index_menu ()
#13 0x0000000000408ad7 in main ()
I hit the issue when moving from screen to screen in the index and it appears
to be trying to fetch a message where the information is not in the
mutt header cache, etc.
Has anyone else seen similar issues? I seem to be able to hit this quite
often and would like to fix the defect.
- Jared
--
Jared Mauch | pgp key available via finger from [email protected]
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
