Bug 714356

Summary: [abrt] claws-mail-3.7.9-2.fc14: memcpy: Process /usr/bin/claws-mail was killed by signal 7 (SIGBUS)
Product: [Fedora] Fedora Reporter: rob.jacko.jackson
Component: claws-mailAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: andreas.bierfert, bugs.michael, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:e7de375cab88672b842ed916930147a19691a89c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:07:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description rob.jacko.jackson 2011-06-18 12:01:45 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 72213 bytes
cmdline: claws-mail
component: claws-mail
Attached file: coredump, 16384000 bytes
crash_function: memcpy
executable: /usr/bin/claws-mail
kernel: 2.6.35.13-91.fc14.i686
package: claws-mail-3.7.9-2.fc14
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 7 (SIGBUS)
release: Fedora release 14 (Laughlin)
time: 1308398077
uid: 500

How to reproduce
-----
1. start claws-mail
2. click yes to "you are in offline mode, do you want to switch to online mode temporarily"
3. the window opens briefly then crashes

Comment 1 rob.jacko.jackson 2011-06-18 12:01:48 UTC
Created attachment 505382 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-06-18 14:24:49 UTC
So, another Google Mail via IMAP crash due to an invalid pointer ("out of bounds" access). There are various other ones, also similar ones such as bug 569478 (which is related to going offline/online, too).

#1  0x0816c9ae in msgcache_get_cache_data_str (src=0xb25a82e7 <Address 0xb25a82e7 out of bounds>, str=0x8daaad0, len=5194, conv=0x0) at /usr/include/bits/string3.h:52
#2  0x0816f2b9 in msgcache_read_cache (item=0x8bf1950, cache_file=0x8b161c0 "/home/jacko/.claws-mail/imapcache/imap.gmail.com/XXXXXX/INBOX/.claws_cache") at msgcache.c:684
#3  0x080fe2ce in folder_item_read_cache (item=0x8bf1950) at folder.c:2638
#4  0x080fe103 in folder_item_scan_full (item=0x8bf1950, filtering=1) at folder.c:2165

Comment 3 Fedora End Of Life 2012-08-16 12:07:34 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping