Why do I get CRC mismatch warning messages from gdb on Red Hat enterprise Linux?

Solution Verified - Updated -

Issue

  • When launching gdb to analyse an application core dump from another machine, I get many CRC mismatch warnings.
Using host libthread_db library "/lib64/libthread_db.so.1".

warning: the debug information found in "/usr/lib/debug//lib64/libnss3.so.debug" does not match "/lib64/libnss3.so" (CRC mismatch).


warning: the debug information found in "/usr/lib/debug/usr/lib64/libnss3.so.debug" does not match "/lib64/libnss3.so" (CRC mismatch).

  • When opening cores from 32 bits applications, gdb prints messages like that:
warning: the debug information found in "/usr/lib/debug/lib/libc-2.5.so.debug" does not match "/lib/libc.so.6" (CRC mismatch).

Opening cores from 64 bits applications does not trigger the printing of those warning messages.

  • Why do I get CRC mismatch warning messages from gdb even though the correct glibc and glibc-debuginfo rpm versions are installed?

Environment

  • Red Hat Enterprise Linux
  • gdb

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.