Perhaps it is a bug unrelated to mmap, that screws up some of your
state, then later it causes the mmap to fail.
Or perhaps the mmap succeeds, but the bytes your are reading are
coming from some other place.
There are many debugging techniques, such as using assertions, guard
malloc etc. But don
> On Feb 5, 2016, at 10:09 AM, Trygve Inda wrote:
>
> It seems like no matter what is in the mmap file, when I read from it I get
> 0x00 for every byte and no error or exception is generated. I can't
> reproduce it as it is very random. Quitting and relaunching solves it.
That sounds strange to
I have image data that is stored in a 150mb file which I use mmap to read.
The image data is pulled into a NSBitmapImageRep pixel by pixel and
eventually shows on the screen. Only a subset of the pixel in the mmap file
are pulled into a single NSBitmapImageRep.
A few customers (and I have seen it
