Interpreting valgrind info

From: Harinder Singh Bawa <harinder.singh.bawa_at_gmail.com>
Date: Fri, 1 Jun 2012 09:52:39 +0200

Hello,

I am running Root code!
I am getting memory leakage problem in my code which runs for sometime and then crash with the following error:

---

Error: Symbol #include is not defined in current scope (tmpfile):1: Error: Symbol exception is not defined in current scope (tmpfile):1: Syntax Error: #include <exception> (tmpfile):1: Error: Symbol G__exception is not defined in current scope (tmpfile):1: Error: type G__exception not defined FILE:(tmpfile) LINE:1 (Long64_t)0***** Interpreter error recovered *****

---

I was suggested to run valgrind and below is the result: Can anybody suggest how to interpret valgrind. What is this suggesting towards!!!

Val grind info:

---

--3044-- REDIR: 0x6f01c00 (operator delete(void*)) redirected to 0x4c701af (operator delete(void*))
==3044==
==3044== HEAP SUMMARY:
==3044== in use at exit: 88 bytes in 1 blocks

==3044== total heap usage: 3 allocs, 2 frees, 276 bytes allocated
==3044==
==3044== Searching for pointers to 1 not-freed blocks

==3044== Checked 201,536 bytes
==3044==
==3044== 88 bytes in 1 blocks are still reachable in loss record 1 of 1

==3044== at 0x4C70D2D: operator new[](unsigned int) (vg_replace_malloc.c:258)
==3044== by 0x8049FBA: main (in /nfs/t3nfs/share/atlas/

ATLASLocalRootBase/x86_64/root/5.28.00-slc5-gcc4.3-i686/bin/root)
==3044==
==3044== LEAK SUMMARY:
==3044== definitely lost: 0 bytes in 0 blocks
==3044== indirectly lost: 0 bytes in 0 blocks
==3044== possibly lost: 0 bytes in 0 blocks
==3044== still reachable: 88 bytes in 1 blocks
==3044== suppressed: 0 bytes in 0 blocks
==3044==
==3044== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 30 from 9)
--3044--
--3044-- used_suppression: 30 dl-hack3
==3044==
==3044== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 30 from 9)

---

Harinder Received on Fri Jun 01 2012 - 09:52:47 CEST