In some cint script I have some class objects which are local to a function. However if there is an error in the function libcint bombs out and the heap is not cleaned thus triggering code guard to report of resource leakages if it is enabled.
I can clean up the heap later for dynamically allocated objects within the class itself but it appears that cint uses the heap to allocate local variables rather than the stack and I still get small resource leakages if the function has an error in it such as an undefined function call. Otherwise if there are no errors in the code there are no problems with resource leakages.
Is there a function I can call that will clean up the heap in case of a major error ??
[quote]Unfortunately G__free_tempobject() is not exported in the libcint.dll [/quote]Humm … strange … It is listed in G__ci.h and is used in ROOT’s libCore (so it seems to be exported).
[quote=“pcanal”][quote]Unfortunately G__free_tempobject() is not exported in the libcint.dll [/quote]Humm … strange … It is listed in G__ci.h and is used in ROOT’s libCore (so it seems to be exported).
Cheers,
Philippe.[/quote]
Hello Philippe
I am using 5.15.174 so maybe that’s the difference or is there some switch when you build cint to enable it ??