Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.47.el6_2.9.i686 libgcc-4.4.6-3.el6.i686 libstdc++-4.4.6-3.el6.i686

Question

CentOS 6.2 + GNU gdb (GDB) Red Hat Enterprise Linux (7.2-50.el6)

When I debug a simple c++ code with GDB, I saw the following warning:

Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.47.el6_2.9.i686 libgcc-4.4.6-3.el6.i686 libstdc++-4.4.6-3.el6.i686 

I have tried the following methods and none of them fix the problems:

1. Search SO

2. yum install glibc

3. debuginfo-install glibc-2.12-1.47.el6_2.9.i686 libgcc-4.4.6-3.el6.i686 libstdc++-4.4.6-3.el6.i686

In fact, when I install those RPM one by one, I just realized that they are installed already.

[root@localhost Excluded]# rpm -ivh glibc-2.12-1.47.el6_2.9.i686.rpm  Preparing...                ########################################### [100%]     package glibc-2.12-1.47.el6_2.9.i686 is already installed [root@localhost Excluded]# ls *.rpm glibc-2.12-1.47.el6_2.9.i686.rpm  libgcc-4.4.6-3.el6.i686.rpm [root@localhost Excluded]# rpm -ivh libgcc-4.4.6-3.el6.i686.rpm  Preparing...                ########################################### [100%]     package libgcc-4.4.6-3.el6.i686 is already installed [root@localhost Excluded]# rpm -ivh libstdc++-4.4.6-3.el6.i686.rpm  warning: libstdc++-4.4.6-3.el6.i686.rpm: Header V4 DSA/SHA1 Signature, key ID 192a7d7d: NOKEY Preparing...                ########################################### [100%]     package libstdc++-4.4.6-3.el6.i686 is already installed     file /usr/lib/libstdc++.so.6.0.13 from install of libstdc++-4.4.6-3.el6.i686 conflicts with file from package libstdc++-4.4.6-3.el6.i686 

Why GDB cannot find it?

Question: Do I have to worry about this issue? If not, how to turn it off? If yes, how to fix it?

Thank you

Answer 1

debuginfo-install is a command of yum-utils, so

1. yum install yum-utils
2. debuginfo-install glibc
3. if the warning's still there, edit /etc/yum.repos.d/CentOS-Debuginfo.repo, set enabled=1

Answer 2

In case, someone else encounters the same issue,

I had updated the glibc and somehow the old ldconfig had been flushed was facing this error while running the application

error while loading shared libraries: libjson-c.so.2: cannot open shared object file: No such file or directory

Even after setting the LD_LIBRARY_PATH it didn't work:

LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH 

Finally the commands below came to the rescue.

// Add you library path here. echo /usr/local/lib >> /etc/ld.so.conf  // And then Run ldconfig to reflect the path ldconfig