I am trying to improve a component library we developed. If I call the library in a console based (text) program, written specifically to test one routine, vTune Lock and Wait analysis do show Worker thread wait/running states and lock transitions. However, when I run the original main GUI based application, vTune Lock and Wait analysis shows absolutely no information. All the Bottom-Up, Caller/Callee and Top-down Tree basically have one row with [Unknown]/[Unknown]/[No call stack information]. The Tasks and Frames shows the work threads are all running between my VTPause() and VTResume() calls, for approximately 10 seconds, and the CPU Usage graph has a realistic graph, but the Thread Concurrency graph is FLAT, there is no Waits region (click on the Waits graph does nothing), and no Thread/Lock transitions are displayed when the Transitions box is checked.
The collection has no error, the resolve process produced no error. The application runs fine, but the collector output (when run in a command prompt) does not appear to look for debug symbols for some dlls which I know are loaded and was running. It does fail to load debug symbols for mscorwks.dll, perfdisk.dll, user32.dll (system / .Net framework dlls), but there are no error messages.
Any idea what I should do to allow me to perform the analysis on the project showing call stacks and lock / waits?