Open jlp765 opened 8 years ago
Is that really a bug though? Memory mapping of files is low level and we give you what the OS supports.
Currently it is an undocumented feature (in the memFiles doco). If it is different on different OS, then that should also be documented.
There should at least be a function that provides (in an OS independent way) the min offset size that can be mapped.
However, it would be much more user friendly to provide the means to map any sized object.
This issue has been automatically marked as stale because it has not had recent activity. If you think it is still a valid issue, write a comment below; otherwise it will be closed. Thank you for your contributions.
The windows call MapViewOfFileEx() has a memory mapping granularity (usually around 4K).
Calls to mapMem for offsets less than the granularity should be mapped internally to offsets in the mem buffer of the MemFile object.
Currently it fails with
for the test