Bug 2955 - double linked list while receiving IMAP messages
Summary: double linked list while receiving IMAP messages
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail
Classification: Unclassified
Component: Folders/IMAP (show other bugs)
Version: 3.9.3
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2013-07-04 15:35 CEST by kardan
Modified: 2013-08-14 10:44 CEST (History)
0 users

See Also:


Attachments
claws --debug + gdb 7.6 trace (3.71 KB, application/octet-stream)
2013-07-04 15:35 CEST, kardan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description kardan 2013-07-04 15:35:09 CEST
Created attachment 1280 [details]
claws --debug + gdb 7.6 trace

Caught another crash due to memory corruption while receiving messages (without UI interaction). I keep the core file untouched in case someone needs specific info.

I do not see, if this is a problem in claws or the used libraries.
Who knows why gdb throws around with dwarfs and what hit my memory this hard that all traces are broken (see attached log).

Error in `/usr/bin/claws-mail': double free or corruption (out): 0x0c198a48
/usr/bin/claws-mail(claws_marshal_VOID__POINTER_INT+0xb2)[0x82c8b88]
...
#1  0xb6da982f in __GI_raise (sig=<error reading variable: Unhandled dwarf expression opcode 0x1>) at ../nptl/sysdeps/unix/sys
v/linux/raise.c:56
#2  0xb6f25ff4 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#3  0xb6df0e62 in malloc_printerr (action=<error reading variable: Unhandled dwarf expression opcode 0x0>, str=<optimized out>
, ptr=<error reading variable: DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjunction with
 DW_OP_piece or DW_OP_bit_piece.>) at malloc.c:4902
#4  0x00000002 in ?? ()
#5  0xb6ee5c50 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

From the trace I would say, there are missing some symbols, but 
ii  libc6-dbg:i386                        2.17-6
Comment 1 Paul 2013-08-14 10:44:57 CEST
re-open only if you can provide clear instructions on what the bug is and how to reproduce it.