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.

Description of problem: When trying to load the crash dump in gdb captured by abrt, following error messages are reported:

warning: Corrupted shared library list: 0x7f1a549fa730 != 0x15062e0

warning: Corrupted shared library list: 0x7f1a549fa730 != 0x15062e0

Following the error, the complete backtrace is not getting generated.

How reproducible: Sometimes

Steps to Reproduce:
Load the attached coredump in gdb for /usr/bin/kdeinit4 and try to generate a backtrace.

Actual results: Corrupted shared Library does not allow generation of complete backtrace.

Expected results: It should be able to generate complete backtrace. 

Additional info: Customer is using NVIDIA drivers, can it lead to package mismatches or corrupting shared library list?

Thank you for the report! I am afraid that ABRT cannot do much in this matter. It might happen that the kdeinit4 process messes up its own memory in the way that the core file cannot be successfully loaded by gdb. Can you please turn of abrt, generate several core files using pure kernel core file handler and try to generate backtrace from each of the core files?

# systemctl stop abrt-ccpp
# mkdir /var/tmp/cores/
# echo "/var/tmp/cores/core.%P" > /proc/sys/kernel/core_pattern
... reproduce the crash
# cd /var/tmp/cores/
# for c in $(ls core*); do gdb -c $c; done

I do not think NVIDIA kernel drivers can break user space process memory. You can try to run kdeinit4 in valgrind to detect memory errors, but that might be extremely time consuming operation.

I am not able to reproduce this problem and it looks like it is third party software issue hence I am closing it.

Please feel free to reopen this bugzilla if you are able to reproduce it.