Re:Compiler bug? Linker bug? Windows Kernel bug
by blattimwind on Monday February 26, 2018 @05:35AM
(#16464382)
Since it's only observed by execution, its entirely possible that the PE loader has been optimized in a low-level fashion leading to bugs that are not exposed in general I/O facilities.
[ Parent
| on HN ]
Re:Compiler bug? Linker bug? Windows Kernel bug
by gmueckl on Monday February 26, 2018 @07:27AM
(#16464802)
My reading is that PE images are memory mapped into RAM instead of being read from disk. This is why they require write locks on the files during execution: the program image is backed from the corresponding file instead of the normal page file.
So my speculation is that this bug is a race condition between the cleanup of a dirty memory mapped section of a file and the reading of the same file contents in a separate mapping.