GNOME Bugzilla – Bug 573032
evolution abort without error message when attampting to display a particular message
Last modified: 2009-02-25 04:07:03 UTC
Steps to reproduce: 1. start evolution 2. with my inbox attempt to display a particular message 3. Stack trace: Here is output when run using strace: *** glibc detected *** strace: malloc(): memory corruption (fast): 0x0000000000ec0460 *** ======= Backtrace: ========= /lib64/libc.so.6[0x38a4a77ec8] /lib64/libc.so.6[0x38a4a7b561] /lib64/libc.so.6(__libc_malloc+0x98)[0x38a4a7ca38] strace[0x408728] strace[0x40598e] strace[0x404696] /lib64/libc.so.6(__libc_start_main+0xe6)[0x38a4a1e576] strace[0x401e69] ======= Memory map: ======== 00400000-00447000 r-xp 00000000 fd:00 129696 /usr/bin/strace 00647000-00648000 rw-p 00047000 fd:00 129696 /usr/bin/strace 00648000-00656000 rw-p 00648000 00:00 0 00847000-00848000 rw-p 00047000 fd:00 129696 /usr/bin/strace 00ec0000-00ee1000 rw-p 00ec0000 00:00 0 [heap] 38a4600000-38a4620000 r-xp 00000000 fd:00 3211265 /lib64/ld-2.9.so 38a481f000-38a4820000 r--p 0001f000 fd:00 3211265 /lib64/ld-2.9.so 38a4820000-38a4821000 rw-p 00020000 fd:00 3211265 /lib64/ld-2.9.so 38a4a00000-38a4b68000 r-xp 00000000 fd:00 3211266 /lib64/libc-2.9.so 38a4b68000-38a4d68000 ---p 00168000 fd:00 3211266 /lib64/libc-2.9.so 38a4d68000-38a4d6c000 r--p 00168000 fd:00 3211266 /lib64/libc-2.9.so 38a4d6c000-38a4d6d000 rw-p 0016c000 fd:00 3211266 /lib64/libc-2.9.so 38a4d6d000-38a4d72000 rw-p 38a4d6d000 00:00 0 38b0400000-38b0416000 r-xp 00000000 fd:00 3211283 /lib64/libgcc_s-4.3.2-20081105.so.1 38b0416000-38b0616000 ---p 00016000 fd:00 3211283 /lib64/libgcc_s-4.3.2-20081105.so.1 38b0616000-38b0617000 rw-p 00016000 fd:00 3211283 /lib64/libgcc_s-4.3.2-20081105.so.1 7f397c000000-7f397c021000 rw-p 7f397c000000 00:00 0 7f397c021000-7f3980000000 ---p 7f397c021000 00:00 0 7f3980f8d000-7f3980f8f000 rw-p 7f3980f8d000 00:00 0 7f3980fa6000-7f3980fa8000 rw-p 7f3980fa6000 00:00 0 7fff88f92000-7fff88fa7000 rw-p 7ffffffea000 00:00 0 [stack] 7fff88ffe000-7fff88fff000 r-xp 7fff88ffe000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] Abort Other information: Rest of strace output is available, but is pretty large.
Created attachment 129430 [details] strace output Entire strace output
Created attachment 129432 [details] This is the message that causes the abort I extracted this message from the Inbox with an editor. I then used the import facility to bring it into evolution. When I attempt to display it, evolution aborts.
Reproduced crash from the mail in comment #2. I don't load images automatically so I had to press Ctrl+I to trigger the crash. Backtrace follows: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb34f0b90 (LWP 6113)] 0x0125da17 in camel_mime_parser_read (parser=0x0, databuffer=0xb34efb80, len=1500) at camel-mime-parser.c:655 655 struct _header_scan_state *s = _PRIVATE (parser);
+ Trace 212875
Thread 21 (Thread 0xb34f0b90 (LWP 6113))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 569700 ***