From: Steve Blinkhorn <steve@pr...> - 2003-03-03 18:36:25
Thanks to those who replied to my original message by personal email.
There have been developments.
To avoid depending on Win2000's environment handling code, I
completely re-implemented my dynamic variable handling using a hash
table. I copy the original environment passed to my program into the
hash table, which I make a fixed size, much larger than needed for the
actual program. Which then crashes at precisely the same point.
The problem is Windows 2000 specific - I don't get it under Unix nor
under NT 4. Because the program does a *lot* of function calls, I
suspect what we have is a memory leak in stack management. To
pursue this further, I would like to take more control over how the
program is loaded. Can anyone familiar with TFM on this topic point
me to the pages I should R? Someone suggested adding:
which doesn't seem to achieve anything, but doesn't cause a problem
either. Nor can I find in in my documentation that refers to it.
Is this recent?
A further complication is that I do use nested functions, which
combined with the dynamic nature of the rest of the code means
enormous numbers of function calls, so any leak is likely to cause a
problem sooner or later....
Steve Blinkhorn <steve@...>