Version-Release number of selected component: claws-mail-3.9.0-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: claws-mail crash_function: re_node_set_insert_last kernel: 3.6.10-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #3 re_node_set_insert_last at regex_internal.c:1342 : #4 calc_inveclosure at regcomp.c:1590 : #5 analyze at regcomp.c:1168 : #6 re_compile_internal at regcomp.c:798 : #7 __regcomp at regcomp.c:500 : #8 subject_get_prefix_length at utils.c:3799 : #10 subject_table_insert at utils.c:3711 : #11 summary_set_ctree_from_list at summaryview.c:3163 : #12 summary_show at summaryview.c:1460 : #13 folderview_selected at folderview.c:2221
Created attachment 688034 [details] File: core_backtrace
Created attachment 688035 [details] File: environ
Created attachment 688036 [details] File: limits
Created attachment 688037 [details] File: backtrace
Created attachment 688038 [details] File: cgroup
Created attachment 688039 [details] File: smolt_data
Created attachment 688040 [details] File: xsession_errors
Created attachment 688041 [details] File: executable
Created attachment 688042 [details] File: maps
Created attachment 688043 [details] File: dso_list
Created attachment 688044 [details] File: open_fds
Created attachment 688045 [details] File: var_log_messages
Created attachment 688046 [details] File: proc_pid_status
Reproducibly? And how? Please don't let us guess too much about what you've tried prior to the crash. | ** (claws-mail:1919): WARNING **: [15:49:36] IMAP error on imap.gmail.com: LOGIN error | (claws-mail:1919): Claws-Mail-CRITICAL **: imap_scan_required: assertion `session != NULL' failed | ** (claws-mail:1919): WARNING **: [15:50:24] IMAP error on imap.gmail.com: STATUS error | #6 re_compile_internal (preg=preg@entry=0x9855e0, pattern=0x10c <Address | 0x10c out of bounds>, pattern@entry=0x1ac0780 "^\\ *((Re\\:\\ ?)|(Re\\[[1-9] | [0-9]*\\]\\:\\ ?)|(Antw\\:\\ ?)|(Aw\\:\\ ?)|(Antwort\\:\\ ?)|(Res\\:\\ | ?)|(Fw\\:\\ ?)|(Fwd\\:\\ ?)|(Enc\\:\\ ?)|(Odp\\:\\ ?)|(Rif\\:\\ ?)|(Sv\\:\\ | ?)|(Vs\\:\\ ?)|(Ad\\:\\ ?)|(\347\255\224\345\244\215\\:\\ ?)|(R\303\251f\\. | \\:\\ ?)"..., length=25687488, syntax=syntax@entry=4436732) at regcomp.c:798 | #10 0x00000000005d9279 in subject_table_insert (subject_table=0x1771cc0, | subject=0x41f7dff8 <Address 0x41f7dff8 out of bounds>, data=0x0, | data@entry=0x1684e40) at utils.c:3711
| #8 0x00000000005d915f in subject_get_prefix_length (subject=0x187eb70 | "[KC-List] SLSP 2013: 2nd call for papers") at utils.c:3799 I've created a test message with that Subject header, but it is not sufficient to make regcomp() crash during memory reallocation. Note that we're in glibc space there. Without any feedback on reproducibility, there's not much we can do. Simply forwarding tickets like this into the upstream bug tracker won't work well either.