g++ -g -pipe -Wall -W -Woverloaded-virtual -fPIC -Iinclude -DG__REGEXP -DG__UNIX -DG__SHAREDLIB -DG__OSFDLL -DG__ROOT -DG__REDIRECTIO -DG__STD_EXCEPTION -pthread -o cint/src/v6_newlink.o -c cint/src/v6_newlink.cxx
cint/src/v6_newlink.cxx: In function void G__set_ioctortype_handler(int (*)(const char*))': cint/src/v6_newlink.cxx:64: error:G__p_i’ undeclared (first use this function)
cint/src/v6_newlink.cxx:64: error: (Each undeclared identifier is reported only once for each function it appears in.)
cint/src/v6_newlink.cxx:64: error: expected `;’ before "octortype_handler"
cint/src/v6_newlink.cxx: At global scope:
cint/src/v6_newlink.cxx:63: warning: unused parameter 'p2f’
make: *** [cint/src/v6_newlink.o] Error 1
during compilation of ROOT I plugged in valgrind in front of call to rootcint_tmp
It looks like some dictionaries may potentially be screwed up if rootcint has unaccounted memory leaks…
Originally the problem started with me getitng errors of old size new size mismatch during creation of large TTrees.
I decided to check my program-ROOT combo with valgrind for memory mishandling. But before doing that I wanted to make sure there are no errors with rootcint that is used to generate dictionaries for root installation, which is rootcint_tmp here…
During creation of my classes dictionaries with rootcint though, I don’t have any errors. So, it must be combo of rootcint_tmp and some root classes that gives these memory leaks.
Feel free to ask whatever you need me to do to sort it out. I am really concerned about correctness of TTrees and I don’t want any memory leaks.
Once this one is resolved I will proceed to valgrinding my program
[quote]g++ -g -pipe -Wall -W -Woverloaded-virtual -fPIC -Iinclude -DG__REGEXP -DG__UNIX -DG__SHAREDLIB -DG__OSFDLL -DG__ROOT -DG__REDIRECTIO -DG__STD_EXCEPTION -pthread -o cint/src/v6_newlink.o -c cint/src/v6_newlink.cxx
cint/src/v6_newlink.cxx: In function void G__set_ioctortype_handler(int (*)(const char*))': cint/src/v6_newlink.cxx:64: error:G__p_i’ undeclared (first use this function) [/quote]
Do you still have this error? If you do, let me know when and where!
[quote]It looks like some dictionaries may potentially be screwed up if rootcint has unaccounted memory leaks… [/quote]This is extremely unlikely! The memory leak only consequence should be that rootcint uses more memory than it could. Even more, in most case the likely is only apparent (i.e. it leaks only because we do not properly clean up at the end of the process).
[quote]==10459== 8 bytes in 2 blocks are definitely lost in loss record 1 of 7
==10459== at 0x3414BC25: calloc (vg_replace_malloc.c:176)
==10459== by 0x81485A3: G__malloc (v6_malloc.cxx:263)
==10459== by 0x81D28E4: G__allocvariable (v6_var.cxx:6252)
==10459== by 0x81C38C6: G__letvariable (v6_var.cxx:2862)
[/quote]
For now please ignore this ‘leak’.
[quote]Originally the problem started with me getitng errors of old size new size mismatch during creation of large TTrees.[/quote]This should not be related to dictionary generation.
[quote]During creation of my classes dictionaries with rootcint though, I don’t have any errors. … [/quote]Your dictionary are problably just fine.