> CMake iterates over the Windows "running object table" (a COM thing) to find > Visual Studio instances to ping to call the reload macro. When something is > dead and stuck in the running object table (which happens occasionally, but > thankfully not frequently) then CMake hangs in that iteration loop waiting > forever for that dead thing to respond. The only way out of that situation > is a reboot or actually killing the process that's really hung. As soon as > that's killed, CMake continues its iteration happily, not realizing it's > been waiting for hours or days... :-) > > So there's an explanation for such mad behavior... even though it's not > going to make anybody happy, at least it's not a mystery. The mystery is why > Outlook was hung in the first place.
I thought that was COM related but I have not looked into COM in years.. > > Have you considered using Thunderbird? :-) > Company policy but I do not usually use the company email system for even work related matters. I do not check outlook often that is why I did not notice.. One reason is they automatically throw away most attachments with no way to get them back and without notifying the sender. That has burned me more than once with companies sending me SDKs in zip files. John _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
