Bug 1005277

Summary: [abrt] claws-mail-3.9.2-7.fc19: re_search_internal: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Andrey V. Henneberg <safir>
Component: claws-mailAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: andreas.bierfert, bugs.michael
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:5094ef095fbb3ec6d2122f9b3cff358e76180b50
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-06 21:38:49 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Andrey V. Henneberg 2013-09-06 14:54:53 UTC 
Description of problem:
As far as I understand it has crashed when network connection was switched off.

Version-Release number of selected component:
claws-mail-3.9.2-7.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/claws-mail
crash_function: re_search_internal
executable:     /usr/bin/claws-mail
kernel:         3.10.10-200.fc19.i686.PAE
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 re_search_internal at regexec.c:711
 #3 __regexec at regexec.c:250
 #4 subject_get_prefix_length at utils.c:3824
 #5 subject_table_lookup at utils.c:3716
 #6 folder_item_scan_full at folder.c:2425
 #7 folder_item_scan at folder.c:2501
 #8 folderview_check_new at folderview.c:1197
 #9 inc_all_account_mail at inc.c:379
 #10 inc_autocheck_func at inc.c:1559
 #16 gtk_main at gtkmain.c:1257
Comment 1 Andrey V. Henneberg 2013-09-06 14:54:58 UTC 
Created attachment 794796 [details]
File: backtrace
Comment 2 Andrey V. Henneberg 2013-09-06 14:55:01 UTC 
Created attachment 794797 [details]
File: cgroup
Comment 3 Andrey V. Henneberg 2013-09-06 14:55:05 UTC 
Created attachment 794798 [details]
File: core_backtrace
Comment 4 Andrey V. Henneberg 2013-09-06 14:55:09 UTC 
Created attachment 794799 [details]
File: dso_list
Comment 5 Andrey V. Henneberg 2013-09-06 14:55:12 UTC 
Created attachment 794800 [details]
File: environ
Comment 6 Andrey V. Henneberg 2013-09-06 14:55:16 UTC 
Created attachment 794801 [details]
File: exploitable
Comment 7 Andrey V. Henneberg 2013-09-06 14:55:19 UTC 
Created attachment 794802 [details]
File: limits
Comment 8 Andrey V. Henneberg 2013-09-06 14:55:24 UTC 
Created attachment 794803 [details]
File: maps
Comment 9 Andrey V. Henneberg 2013-09-06 14:55:27 UTC 
Created attachment 794804 [details]
File: open_fds
Comment 10 Andrey V. Henneberg 2013-09-06 14:55:34 UTC 
Created attachment 794805 [details]
File: proc_pid_status
Comment 11 Andrey V. Henneberg 2013-09-06 14:55:38 UTC 
Created attachment 794806 [details]
File: var_log_messages
Comment 12 Michael Schwendt 2013-11-06 21:38:49 UTC 
> As far as I understand it has crashed when network connection was switched off.

Then it's the old instability when losing/interrupting networking, and the crash (in memory management) is just a side-effect. There are various upstream tickets about such crashes already.

| #0  0x49544100 in _int_malloc (av=av@entry=0x49688420 <main_arena>,
| bytes=bytes@entry=1048) at malloc.c:3631