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.

User has repeated messages in the format:

Jun 14 10:52:12 mgtlxp01 kernel: abrt-hook-ccpp[4077]: segfault at a0 ip 00000038b6b336bf sp 00007ffff2410b28 error 4 in libc-2.12.so[38b6a00000+18a000]
Jun 14 10:52:12 mgtlxp01 kernel: Process 4077(abrt-hook-ccpp) has RLIMIT_CORE set to 1
Jun 14 10:52:12 mgtlxp01 kernel: Aborting core

  I see that the same pattern was commented in rhbz #652338
and said to be a known issue, but the fix was an update from
abrt-1.1.13 to abrt-1.1.14.

  Can you please clarify what was the patch, and/or also check
if abrt-2.0.8-6.el6 (rhel 6.3) might have the same issue?

  As extra information, checking logs, there is a third party
process that crashes frequently. On older logs it was generating
a crash report, but dumps started increasing in size, until above
1.8G and when the "kernel: Aborting core" became more frequent.

Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
 
The official life cycle policy can be reviewed here:
 
http://redhat.com/rhel/lifecycle
 
This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
 
https://access.redhat.com