Re: Possible heap problem on Windows, help sought

["Alex R. Mosteo" <devnull@mailinator.com>]

Duncan Sands wrote:

>> Well I made a small test program using my ordinary compilation options
>> (-g -O2 -gnato -fstack-check) and it happily allocated and used 300 MB
>> of heap, as I asked it to, so it seems that this is not a heap problem.
>> Sorry for a mistaken hypothesis, I should have checked it before posting
>> my question. But the problem remains and any advice will be gratefully
>> received, although I now suspect that the cause may be a programming
>> error, a Heisenbug that disappears in the debugger and does not manifest
>> on Linux for some reason.
> 
> It could well be memory corruption or the use of an uninitialized
> variable. These both have a tendency to manifest themselves differently in
> the debugger. Try running your program under valgrind.

Also check Gnat.Debug_Pools (Is it already in Gnat 3.15p?)

With the default stack size, a windows program will lock when creating the
~250 task, but you said you didn't use tasks.