Ok i will recompile and try to isolate it.
Since I didn't see them before it.
I will revert the code to see too.
Ron.
Post by Benoît MinisiniPost by RonRevision #5598 and #5600 made Gambas3 stable.
gbx3: warning: 35 allocation(s) non freed.
How can I check what they are?
Run valgrind?
Regards,
Ron_2nd.
This is a memory leak in the interpreter or a component detected by the
interpreter.
Alas valgrind won't help there.
It's the most difficult bug to fix.
The most important is trying to reproduce it reliably. If you can, then
just explain me how. But I guess you won't be able, so let's go the hard
way: recompiling the interpreter by enabling memory allocation debugging.
To do that, edit the /share/gb_alloc.h file at line 29 to replace
"#define DEBUG_MEMORY 0" by "#define DEBUG_MEMORY 1".
Then recompile and install the interpreter.
Then run your project: all allocation routines will generate a trace on
$ cd /path/to/DomotiGa
$ gbx3 > gbx.out 2>&1
Then wait until you stop the program and get the non-freed allocation
warning, and send me the 'gbx.out' file. Beware that it may be big!
Regards,
--
Benoît Minisini
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Gambas-user mailing list
https://lists.sourceforge.net/lists/listinfo/gambas-user