Valgrind doesn't show anything (except some false positives)...
Also I have this same warning with my test project, which I use to test
newly compiled revision.
My compilation script:
#!/bin/sh
killall gbr3
sleep 1
sudo rm -f /usr/local/bin/gbx3 /usr/local/bin/gbc3 /usr/local/bin/gba3
/usr/local/
Valgrind is also a nice tool. For each malloc() that has not been free():d,
it will list how the runtime stack looked like when the unfreed memory
chunk was allocated. If you use it with Gambas, you might need to disable
the memory pooling system Gambas uses, otherwise you can get strange
results..
Thanks!
Jussi
On Sun, Mar 11, 2012 at 17:03, Emil Lenngren wrote:
> The interpreter has support for debugging memory using some flags. Then you
> can see in which functions borrows/releases are made. Look in the source
> code what the flags are and compile gbx with them enabled ;)
>
> /Emil
>
>
The interpreter has support for debugging memory using some flags. Then you
can see in which functions borrows/releases are made. Look in the source
code what the flags are and compile gbx with them enabled ;)
/Emil
2012/3/11 Jussi Lahtinen
> Hi!
> Is it possible to have more information about
Hi!
Is it possible to have more information about non freed allocations?
Pointer name, object where allocation is done or something that would help
to find the problem?
Since I don't think I have any non freed allocations...
Jussi
--
