Bug 680780

Summary: [abrt] claws-mail-3.7.8-3.fc14: imap_threaded_select: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: gerfert
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:4809dc5a82997931124411498401064badac1d06
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:05:26 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 gerfert 2011-02-27 17:43:45 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 33700 bytes
cmdline: claws-mail
component: claws-mail
Attached file: coredump, 15851520 bytes
crash_function: imap_threaded_select
executable: /usr/bin/claws-mail
kernel: 2.6.35.11-83.fc14.i686
package: claws-mail-3.7.8-3.fc14
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298827799
uid: 500

How to reproduce
-----
1. i began rebuilding my imap directories tree
2. and claws-mail crashed
3.

Comment 1 gerfert 2011-02-27 17:43:48 UTC
Created attachment 481262 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-02-27 18:54:46 UTC
> How to reproduce
> -----
> 1. i began rebuilding my imap directories tree
> 2. and claws-mail crashed

That's what you did, but the key question is: Is it enough to reproduce the crash _always_? I assume it crashed just once (because folder tree rebuilding works here with two different IMAP servers).

[...]

| #0  0x0822d185 in imap_threaded_select (folder=0x8908e70, 
| mb=0x873e2b0 "INBOX", exists=0xbfb278a8, recent=0xbfb278a4,
| unseen=0xbfb278a0, uid_validity=0xbfb2789c,
| can_create_flags=0xbfb27898,
| ok_flags=0x89761e8) at imap-thread.c:1420

imap-thread.c is Claws Mail's src/etpan/imap-thread.c where it does:

|	imap = get_imap(folder);
...
|  	if (!imap || imap->imap_selection_info == NULL)
|		return MAILIMAP_ERROR_PARSE;
|	
|	* exists = imap->imap_selection_info->sel_exists;

The last line is 1420. So, it performs a NULL check for the "imap" pointer and the imap_selection_info pointer. That one is maintained by libetpan. Both must be none-NULL, or else it would have returned earlier. Then in line 1420, "exists" is a pointer to gint, so it would copy an integer. The pointer is created earlier in the backtrace as address of a gint on local stack.

It may make sense to look at recent changes in libetpan cvs.

Comment 3 Fedora End Of Life 2012-08-16 12:05:30 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