Re: g_spawn and files left locked on windows.



The process had finished, and that was why I was puzzled.

But had the process perhaps started some child process that had
(unintentionally) inherited the file handle, and that child process
was still running?

Please install Process Explorer from sysinternals.com and use its
"Find>Find Handle or DLL" functionality to find out open handles to a
file. Process Explorer is an extremely useful tool in many other ways,
too.

--tml



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]