3 ms·
Still a linker bug to me. Where did it became a kernel bug? Looks like wrong usage of memory-mapped I/O, not like a bug in memory-mapped I/O itself.
by rurban 9y ago
Still a linker bug to me. Where did it became a kernel bug?
Looks like wrong usage of memory-mapped I/O, not like a bug in memory-mapped I/O itself.
- brucedawson 9y agoThe linker did nothing wrong. It wrote to a file using memory mapped I/O. Shortly afterwards the build system tried to run the just-linked file. This is supposed to work. It usually does. Due to this bug it occasionally doesn't. The linkers are getting a compatibility hack (FlushFileBuffers call) but this is not supposed to be necessary, by the file-system contract.