Massif is saying that I have allocated a (quite large) std::vector inside my `main' function [1]. The vector template is not used at all in the file which declares the main function.
Is this vector coming from a static initializer, then? How can I identify the location of the allocation? This is with valgrind-3.5.0 on a debian stable, x86_64 installation. -tom [1] 20 2,008,492,212 134,862,424 134,564,847 297,577 0 99.78% (134,564,847B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc. ->49.76% (67,108,864B) 0x4EA992E: std::vector<unsigned char, std::allocator<unsigned char> >::_M_fill_insert(__gnu_cxx::__normal_iterator<unsigned char*, std::vector<unsigned char, std::allocator<unsigned char> > >, unsigned long, unsigned char const&) (new_allocator.h:92) | ->49.76% (67,108,864B) 0x1989D998: ??? | | ->49.76% (67,108,864B) 0x1980D935: ??? | | ->49.76% (67,108,864B) 0x19900A89: ??? | | ->49.76% (67,108,864B) 0x19910CE4: ??? | | ->49.76% (67,108,864B) 0x197D9DF1: ??? | | ->49.76% (67,108,864B) 0x400D384: _dl_catch_error (in /lib/ld-2.7.so) | | ->49.76% (67,108,864B) 0x4011119: _dl_open (in /lib/ld-2.7.so) | | ->49.76% (67,108,864B) 0xF720FB9: dlopen_doit (in /lib/libdl-2.7.so) | | ->49.76% (67,108,864B) 0x400D384: _dl_catch_error (in /lib/ld-2.7.so) | | ->49.76% (67,108,864B) 0xF72136A: _dlerror_run (in /lib/libdl-2.7.so) | | ->49.76% (67,108,864B) 0xF720F1F: dlopen@@GLIBC_2.2.5 (in /lib/libdl-2.7.so) | | ->49.76% (67,108,864B) 0x50CC2E7: PluginManager::PluginOpen(std::string const&) (PluginManager.C:1486) | | ->49.76% (67,108,864B) 0x50CC5CC: PluginManager::LoadSinglePlugin(int) (PluginManager.C:982) | | ->49.76% (67,108,864B) 0x50CC2A4: PluginManager::PluginAvailable(std::string const&) (PluginManager.C:197) | | ->49.76% (67,108,864B) 0x4E601D9: RPCExecutor<PreparePlotRPC>::Execute(PreparePlotRPC*) (Executors.h:414) | | ->49.76% (67,108,864B) 0x68764C6: Subject::Notify() (Subject.C:188) | | ->49.76% (67,108,864B) 0x67A1CCB: AttributeSubject::Notify() (AttributeSubject.C:99) | | ->49.76% (67,108,864B) 0xA2CFBE0: MPIXfer::Process() (MPIXfer.C:331) | | ->49.76% (67,108,864B) 0x4E5F3EF: Engine::PAR_EventLoop() (Engine.C:1462) | | ->49.76% (67,108,864B) 0x40BD24: main (main.C:316) ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
