-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.1.2
-
Component/s: Diagnostics, Logging
-
Environment:Windows
-
Fully Compatible
-
Windows
If a second or later thread calls printStackTrace() on Windows while a first thread is in that code:
1) The later call may fail in its call to SymInitialize(), so no stack trace will be displayed;
2) Stack trace lines will be interspersed, making the traces hard to read.
This has happened a few times in Buildbot. So far, it does not appear to crash or cause other problems.