Hi, I have the same problem with mutt 1.5.18-6 under debian lenny: at random times mutt looses it's connection and gives a "tls_socket_write" error.
Lowering `$imap_keepalive' to a value of 120, 60 or even 10
does not solve this problem for me.
I hope that the gdb backtrace output will prove to be
an additional help in tracing this bug.
If any additional info is needed, please ask.
grtz
Steven
-- backtrace from gdb follows --
tls_socket_write (Error in the push function.)
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7f9f54e41700 (LWP 26782)]
0x00007f9f53893515 in send () from /lib/libc.so.6
(gdb) backtrace
#0 0x00007f9f53893515 in send () from /lib/libc.so.6
#1 0x00007f9f53f8b65a in _gnutls_io_write_buffered (session=0xad6d90,
iptr=<value optimized out>, n=23) at gnutls_buffers.c:780
#2 0x00007f9f53f88601 in _gnutls_send_int (session=0xad6d90,
type=GNUTLS_ALERT, htype=<value optimized out>, _data=0x7fff5cf6dfa0,
sizeofdata=<value optimized out>) at gnutls_record.c:437
#3 0x00007f9f53fa66e0 in gnutls_alert_send (session=0xad6d90, level=<value
optimized out>, desc=<value optimized out>)
at gnutls_alert.c:134
#4 0x00007f9f53f8890f in gnutls_bye (session=0xad6d90, how=GNUTLS_SHUT_RDWR)
at gnutls_record.c:229
#5 0x0000000000489f57 in tls_socket_close (conn=0x8448a0) at
../mutt_ssl_gnutls.c:297
#6 0x00000000004876c4 in mutt_socket_close (conn=0x8448a0) at
../mutt_socket.c:81
#7 0x00000000004881e1 in mutt_socket_write_d (conn=0x8448a0, buf=<value
optimized out>, len=<value optimized out>,
dbg=<value optimized out>) at ../mutt_socket.c:130
#8 0x000000000048ff4f in imap_exec (idata=0x879ed0, cmdstr=<value optimized
out>, flags=0) at ../../imap/command.c:251
#9 0x0000000000490aeb in imap_check_mailbox (ctx=<value optimized out>,
index_hint=<value optimized out>, force=0)
at ../../imap/imap.c:1386
#10 0x000000000041db6d in mutt_index_menu () at ../curs_main.c:498
#11 0x0000000000439fed in main (argc=3, argv=0x7fff5cf6f488) at ../main.c:1005
signature.asc
Description: Digital signature
