It is not a problem it just makes it a bit tricky tracking memory usage
because of the delay between releasing the memory and it the reported
heap usage decreasing. I haven't had a good look at the source but
maybe there is some way to take these pending releases into account.
Thanks for your
If the default memory manager for FP creates a heap for each thread,
what happens if an object is created in one thread and freed by another ?
Also, do calls to New () allocate space on the thread heap or just
allocated by the OS ?
---
This email has been checked for viruses by Avast antiviru
Jonas - -O- option didn't do any different but I did bite the bullet and
upgrade to 3.0 which does solve the problem.
Thanks.
On 25/01/2017 6:54 AM, Jonas Maebe wrote:
On 23/01/17 10:17, Terry Mead wrote:
When compiled and run under Windows it generates the stack trace:
Runtime error 2
Gentlemen,
I'm a new poster to the mail list. I have a problem logging call stack
trace info following an exception.
The following simple program generates a divide by zero error.
PROGRAM Test;
VAR i, j, k : Integer;
PROCEDURE test1;
BEGIN
i := i - 1;
k := j DIV i;
END; {test}
