The mmap fails before the thread is started.
The one device runs WinCE Core 4.2 and the other WinCE Core 5.0
On Wed, Sep 10, 2008 at 11:39 AM, Sébastien Lorquet <[EMAIL PROTECTED]>wrote:
>
> http://www.google.fr/search?hl=fr&q=wince+virtual+memory+problem&btnG=Rechercher&meta=
>
> http://blogs.m
http://www.google.fr/search?hl=fr&q=wince+virtual+memory+problem&btnG=Rechercher&meta=
http://blogs.msdn.com/ce_base/archive/2006/10/30/What-is-Virtual-Memory.aspx
http://blogs.msdn.com/kitlfirst/archive/2006/01/31/520197.aspx
wince < 6 has a 32 MB virtual address space
it's 2GB on wince >=6
but
According to Remote Process Viewer it loads only coredll.dll and that was at
address 0x03f7. So 64MB is gone. Perhaps only 512MB is available as
address space due to some limitation of the ARM4 and / or WinCE kernel ?
On Wed, Sep 10, 2008 at 10:17 AM, Sébastien Lorquet <[EMAIL PROTECTED]>wrote
This may be linked to the virtual memory space available in your process.
The 2GB virtual memory space of each process is used by a lot of things,
including your actual binary and all DLLs loaded at this time.
IIRC the binary is loaded at low adresses but the DLLs are loaded at high
adresses, and
My program maps a file into memory using the code below. Being a 32 bit
architecture I expected to be able to map files of close to 2GB. I am
however only able to map files of around 410MB. Has anyone any experience in
mapping files of this size and larger ?
HANDLE gmap = CreateFileForMapping (f
