Comment 8 for bug 1377113

> I have vast number of threads.

If many threads are already running then perhaps its implausible for this to be the first call to epicsTime::epicsTime and therefore my scenario in comment 5 is perhaps also appearing now to be less likely.

Changing to "static epicsTimeLoadTimeInit lti" might rearrange memory so that the already instantiated object doesn't become an unlucky recipient for corruption?

A tool like valgrind might be helpful. On windows there are various commercial products like purify and the intel tools. The commercial products tend to be quite compiler version specific.

This web site suggests that valgrind might also be run from a mingw installation? The win32-x86-mingw build is using gcc but is otherwise quite similar to the native windows port of EPICS that is used with win32-x86 (and the MS compiler).

http://sourceforge.net/p/valgrind4win/wiki/DevelopmentEnvironment/