On 21 May 2004 at 16:30, Earnie Boyd wrote:
> Is example1.exe a msys-1.0.dll dependent binary?
> I've stated before that I'm not really interested in supporting someone
> else's use of the msys runtime;
Fair enough - I thought I'd ask anyway, since the same programs,
compiled for Mingw and Cygwin, work perfectly fine and don't exhibit
> however, you should check your use of the memory heap. You've
> exceeded the amount of space allocated for your use.
That is what the Msys system has decided - but the test program does
not (at least, it is not supposed to) use much memory at all. Indeed,
all it does is to use the functionality of a (Pascal) class library
that I am building to create a top-level window that does nothing. I am
not sure however how to check my use of the memory heap or how such a
trivial program could exceed the allocated heap space (where is the
heap space allocated, and how much is allocated?).
I am trying to support all Win32 gnu platforms with this class library.
I have checked the header flags in the executable for reserved and
allocated stack and heap space. These are exactly the same in the
Cygwin, Mingw, and Msys executable (as they should be), since the code
is exactly the same, and uses the same Winapi calls. So something is
amiss somewhere (perhaps in the Msys dll, or the Pascal runtime
library). Perhaps I should just stick to testing under Cygwin and Mingw
- but it would be a shame to abandon Msys if the problem can easily be
Best regards, The Chief
Prof. Abimbola A. Olowofoyeku (The African Chief)