This is the mail archive of the
mailing list for the Cygwin project.
RE: Memory Management on AMD64 in 32-bit mode
- From: "Benson Margulies" <bim2003 at basistech dot com>
- To: <jurgen dot defurne at philips dot com>,<cygwin at cygwin dot com>
- Date: Tue, 9 Dec 2003 06:57:49 -0500
- Subject: RE: Memory Management on AMD64 in 32-bit mode
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