Memory Management on AMD64 in 32-bit mode

[Benson Margulies]

The error message rather unambiguously indicates that VirtualAlloc is
returning 0 with GetLastError() == 0. The call in question calls
VirtualAlloc with parameters derived from a call to VirtualQuery against
some stack storage. It seems that this version of Windows is not
altogether pleased to see a call to VA against already reserved storage.
It is also not altogether displeased.

Can someone explain the design of the path of code in stack allocation
that calls VQ and then runs around and calls VA?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/