I haven't looked at this yet -- I've only isolated the problem message
and performed a backtrace. The message in question has been quarantined
in the Test Messages room (the subject is "CAVE...").
When this message is read using webcit stable-78x, webcit dies in an
active loop. The looping thread was interrupted and produced the
following backtrace:
GET /mimepart/2840436/2/101_0091.JPG HTTP/1.1
(gdb) thread 7
[Switching to thread 7 (Thread 0xb6d20b90 (LWP 28843))]#0 0x008d3402 in
__kernel_vsyscall ()
(gdb) bt
#0 0x008d3402 in __kernel_vsyscall ()
#1 0x006a1afb in read () from /lib/libpthread.so.0
#2 0x0011c389 in StrBufReadBLOB (Buf=0x8297f68, fd=0x8296724, append=1,
nBytes=1168502, Error=0xb6d20208)
at lib/stringbuf.c:3676
#3 0x08056baf in serv_read_binary (Ret=0x8297f68, total_len=1168502,
Buf=0x829fdd8) at tcp_sockets.c:370
#4 0x08067043 in mimepart (force_download=0) at
messages.c:1572
#5 0x080671b2 in view_mimepart () at messages.c:1662
#6 0x08052159 in session_loop () at webcit.c:726
#7 0x080501f4 in context_loop (Hdr=0xb6d20324) at context_loop.c:611
#8 0x080a2d3c in worker_entry () at sysdep.c:246
#9 0x0069a832 in start_thread () from /lib/libpthread.so.0
#10 0x00605e0e in clone () from /lib/libc.so.6
