Wed 24 Sep 2008 07:51:25 AM UTC, original submission:
Hi,
looks like there's a small memleak:
==6082== 256 bytes in 4 blocks are definitely lost in loss record 3 of 7
==6082== at 0x4C232D5: operator new(unsigned long) (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==6082== by 0x4ECA8E9: certi::ObjectClass::registerObjectInstance(unsigned long, certi::Object*, unsigned long) (ObjectClass.cc:731)
==6082== by 0x4ECF553: certi::ObjectClassSet::registerObjectInstance(unsigned long, certi::Object*, unsigned long) (ObjectClassSet.cc:512)
==6082== by 0x4ED8209: certi::RootObject::registerObjectInstance(unsigned long, unsigned long, unsigned long, char const*) (RootObject.cc:257)
==6082== by 0x420275: certi::rtig::Federation::registerObject(unsigned long, unsigned long, char const*) (Federation.cc:1400)
==6082== by 0x430666: certi::rtig::FederationsList::registerObject(unsigned long, unsigned long, unsigned long, std::string) (FederationsList.cc:394)
==6082== by 0x43BC1A: certi::rtig::RTIG::processRegisterObject(certi::Socket, certi::NetworkMessage) (RTIG_processing.cc:774)
==6082== by 0x432E1C: certi::rtig::RTIG::chooseProcessingMethod(certi::Socket, certi::NetworkMessage) (RTIG.cc:265)
==6082== by 0x4335C3: certi::rtig::RTIG::processIncomingMessage(certi::Socket*) (RTIG.cc:573)
==6082== by 0x437946: certi::rtig::RTIG::execute() (RTIG.cc:494)
==6082== by 0x432138: main (main.cc:96)
Testcase: Start rtig with valgrind and let connect billboard test. Then stopp rtig with CTRL+C
|