Windows is well-known (I wouldn't say documented necessarily, but it seems everyone has run into this problem before) where there is a very short window after a process exits where some of the handles that were used by the file (e.g. open files, the image file itself, etc) are still locked by the operating system. It doesn't happen every time, or even on every machine (I've never been able to reproduce Adrian's problem on my Windows 10 machine, for example)
Maybe it's due to the search indexer, maybe it's due to antivirus, maybe it's due to a bug in the kernel. LLVM just had a similar problem just this week and fixed it with a similar workaround ( http://llvm.org/viewvc/llvm-project?rev=246708&view=rev) On Fri, Sep 4, 2015 at 12:45 PM Stephane Sezer <s...@cd80.net> wrote: > sas added a subscriber: sas. > sas added a comment. > > Can you just explain why this race happens? > Otherwise, looks good. > > > http://reviews.llvm.org/D12641 > > > >
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
