Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Previously, the array that stores mutt message headers did not properly handle empty header entries. This could cause mutt to terminate unexpectedly with a segmentation fault when a change of message IDs occurred on the IMAP server, for example when the IMAP server was connected with multiple clients while removing messages through one of them. In this update, the handling of empty headers has been optimized and sorting messages in the array has been streamlined. As a result, multiple connected clients now synchronize correctly.
DescriptionStanislaw Gruszka
2011-03-24 09:38:16 UTC
Created attachment 487266[details]
abrt.log
Description of problem:
See attached abrt.log
How reproducible:
Happens once, I did not try to reproduce.
Comment 2RHEL Program Management
2011-03-24 10:07:49 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 5RHEL Program Management
2011-07-06 00:07:45 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6Stanislaw Gruszka
2011-08-14 11:55:22 UTC
Created attachment 518178[details]
patched mutt core dump on Fedora 14
This core dump is on patched mutt from F-14.
Patch did not help. I mange to reproduce the problem, seem it must be more than 1500 messages in the mail box. I'm not going to purge my pop3 mbox, so will be able now to test other patches or provide more info.
> Core was generated by `mutt -f pops://stf_xl.pl'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x080b8b6c in find_subject (ctx=0x920bd88, init=<value optimized out>) at thread.c:433
> 433 !tmp->fake_thread && /* don't match pseudo threads */
> Missing separate debuginfos, use: debuginfo-install glibc-2.13-1.i686 krb5-libs-1.8.2-7.fc14.i686 nss-softokn-freebl-3.12.9-2.fc14.i686 openssl-1.0.0c-1.fc14.i686
> (gdb) bt
> #0 0x080b8b6c in find_subject (ctx=0x920bd88, init=<value optimized out>) at thread.c:433
> #1 pseudo_threads (ctx=0x920bd88, init=<value optimized out>) at thread.c:503
> #2 mutt_sort_threads (ctx=0x920bd88, init=<value optimized out>) at thread.c:960
> #3 0x080b6015 in mutt_sort_headers (ctx=0x920bd88, init=<value optimized out>) at sort.c:297
> #4 0x0808ea67 in mx_sync_mailbox (ctx=0x920bd88, index_hint=0xbfd3d260) at mx.c:1182
> #5 0x08066091 in mutt_index_menu () at curs_main.c:1034
> #6 0x08082e6d in main (argc=1, argv=0xbfd3e3c4) at main.c:1020
> (gdb) list
> 428 ctx->subj_hash->nelem);
> 429 for (ptr = ctx->subj_hash->table[hash]; ptr; ptr = ptr->next)
> 430 {
> 431 tmp = ((HEADER *) ptr->data)->thread;
> 432 if (tmp && tmp != cur && /* don't match the same message */
> 433 !tmp->fake_thread && /* don't match pseudo threads */
> 434 tmp->message->subject_changed && /* only match interesting replies */
> 435 !is_descendant (tmp, cur) && /* don't match in the same thread */
> 436 (date >= (option (OPTTHREADRECEIVED) ?
> 437 tmp->message->received :
Comment 7Stanislaw Gruszka
2011-08-14 12:00:31 UTC
Oops, sorry above attachment was intended for bug 674271.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-0945.html
Created attachment 487266 [details] abrt.log Description of problem: See attached abrt.log How reproducible: Happens once, I did not try to reproduce.