From: Nuno L. <nun...@sa...> - 2007-03-29 22:04:29
|
Hi, I had the very same problem because I was issuing a chroot() call before calling dlopen. If that is your case, well this is a known bug. If not, check if you are *not* calling dlclose (or any error after dlclose won't have the symbols name). Nuno ----- Original Message ----- From: "Jojy Varghese" <Joj...@sy...> To: <val...@li...> Sent: Thursday, March 29, 2007 10:53 PM Subject: [Valgrind-users] Shared objects Hi I am a Valgrind novice and was trying to track down memory lean in our application. Now, we have a lot of shared libraries(in fact all our modules are shared). According to the FAQ, we are required to NOT unload(dlclose) the loaded modules before exit. Now, we dont close the loaded module because we dont care since the process is dying anyways. Given this scenario, should I still expect the memleak information having lots of unresolved symbols? This is an example of the output from the "memcheck" module. ==2448== 1,200 bytes in 60 blocks are still reachable in loss record 135 of 146 ==2448== at 0x401EC9C: operator new(unsigned) (vg_replace_malloc.c:163) ==2448== by 0x4B0BB49: ??? ==2448== by 0x807A23E: iml::CComponentManager::CreateInstance(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, iml::IMKnown**) (CComponentManager.cpp:25) ==2448== by 0x4AFFA99: ??? ==2448== by 0x4AFFC5B: ??? ==2448== by 0x4AFFC5B: ??? ==2448== by 0x4B00B5A: ??? ==2448== by 0x80765E4: iml::BootstrapServiceManager(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&) (StartupShutdown.cpp:276) ==2448== by 0x80700D2: wmain(int, wchar_t**) (VectrixMain.cpp:215) ==2448== by 0x8070832: main (VectrixMain.cpp:140) As you can see, there are a lot of "???" which we would like to know the value of. Is there any other thing I should be doing? Other details: OS: Fedora 5 Arch: Intel x86 thanks in advance |