Re: Fw: [email protected]

On Fri, 26 Dec 2014 13:18:28 +0100, Nithi G wrote:
> Kindly update the status on the same.This is quite urgent and it will be
> appreciated if provide the solution immediately

What is specifically the problem?

BTW the messages like
	warning: Ignoring non-absolute filename: <libmpcontainer.so>
	Missing separate debuginfo for libmpcontainer.so
	Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/43/d10324cf3cd0a20af7c6af9f18e45689fe2ee3
are specific to Fedora/RHEL and not suitable for this upstream mailing list.

The message
	Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.132.el6.x86_64 libaio-0.3.107-10.el6.x86_64 libgcc-4.4.7-4.el6.x86_64 libstdc++-4.4.7-4.el6.x86_64 numactl-2.0.7-6.el6.x86_64
says clearly what you should do, why haven't you done it yet?  And it is also
specific to Fedora/RHEL and not suitable for this upstream mailing list.

The messages like
	Reading symbols from /apprate1/rateadm/lib/rhel62_x86.x/librcc_xbalance.so...(no debugging symbols found)...done.
show what your libraries do not have debug info, you should either recompile
them with -g or turn off their stripping or to supply their separate debug
info for example as file:
	/apprate1/rateadm/lib/rhel62_x86.x/librcc_xbalance.so.debug

But despite these installation problems finally you get the correct prompt:
	#0  0x000000310920f5db in raise () from /lib64/libpthread.so.0
	(gdb)
so just type "backtrace" there - or what do you want else?
Just due to the missing debug info function parameters, local variables etc.
will not be shown.  But sometimes they are not needed for fixing a crash.


Jan