On Mon, 6 Sep 2010, Brian Winfrey wrote:
I have a TestCase that has this issue. If I call obj.Free, I am
unable to step into the Destroy method and heaptrc indicates a memory
leak. If I call obj.Destroy everything works as expected. Following
the call to Free -
... if (obj nil) then
Michael,
pass OPT=3D-gl to the make command line, maybe
DEBUG=3D1 also works
I don't know what this OPT is. Where can I find out more.
Thanks,
Brian
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
On Tue, 7 Sep 2010, bwCode4U wrote:
Michael,
pass OPT=3D-gl to the make command line, maybe
DEBUG=3D1 also works
I don't know what this OPT is. Where can I find out more.
The makefile uses several variables to construct a command-line when compiling
units and programs.
the contents of
I have a TestCase that has this issue. If I call obj.Free, I am
unable to step into the Destroy method and heaptrc indicates a memory
leak. If I call obj.Destroy everything works as expected. Following
the call to Free -
... if (obj nil) then obj.Destroy;
it would seem that the object must be
