Red Hat Bugzilla – Bug 86413
glibc 2.3.2-4.80 crash memprof
Last modified: 2014-06-18 05:07:28 EDT
Description of problem: When I upgrade glibc from 2.2.93-5 to 2.3.2-4, memprof cannot check memory leak or generate profile. When I fallback to use 2.2.93-5, memprof works again. Version-Release number of selected component (if applicable): memprof-0.5.0-2.i386.rpm glibc-2.3.2-4.80.i686.rpm glibc-common-2.3.2-4.80.i386.rpm glibc-devel-2.3.2-4.80.i386.rpm nscd-2.3.2-4.80.i386.rpm How reproducible: I have only one machine with redhat 8.0, and it ALWAYS got the problem described above. Steps to Reproduce: 01. download glibc*2.3.2-4.80*.rpm and nscd-2.3.2-4.80.i386.rpm from updates.redhat.com 02. rpm -Fvh *.rpm 03. rpm -qa | grep glibc // to confirm glibc is updated 04. rpm -qa | grep nscd // to confirm nscd is update 05. reboot the machine // I think it is safer to reboot .... 06. write a simple program with memory leak 07. recompile and link it with -g 08. use memprof to check memory leak 09. -->> cannot check memory leak or profile 10. repeat 5 to 8 11. -->> same problem 12. rpm -Uvh --force glibc-2.2.93-5.i686.rpm glibc-common-2.2.93-5.i386.rpm glibc-devel-2.2.93-5.i386.rpm 13. reboot the machine 14. recompile and link the same source with -g again 15. memprof can check the memory leak Actual results: 1. after upgrade to glibc 2.3.2-4.80, memprof cannot generate the memory leak report or profile report after running a program Expected results: 1. memprof can generate the reports Additional info:
Created attachment 90693 [details] a simple program where memory leak can't be detected after glibc upgraded to 2.3.2-4.80 it can be built with "g++ -g AA.cpp" and then run by "memprof ./a.out"
This basically is "not suprising" - memprof is very fragile to changes in libc; you might want to try the memprof from Rawhide ... it might work better with the newer libc.
memprof-0.5.1-3 from rawhide has the same problem )-:
There is a possible workaround. Just do not let the target program end, like adding a scanf("%d", &a); at the end of the program. Then I can run memprof for memory leack checking
On which versions does this workaround work? On RHEL 3 (memprof-0.5.1-3, glibc-2.3.2-95.3) I don't see any difference at all just by adding the scanf line in the end (right before the return) to the test progran in comment #1
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Red Hat apologizes that these issues have not been resolved yet. We do want to make sure that no important bugs slip through the cracks. Please check if this issue is still present in a current Fedora Core release. If so, please change the product and version to match, and check the box indicating that the requested information has been provided. Note that any bug still open against Red Hat Linux on will be closed as 'CANTFIX' on September 30, 2006. Thanks again for your help.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Closing as CANTFIX.