Comments
Sort by recent activity
Hi,
thank you for the suggestion concerning the thread name. We will take a look if we can change the order of settings the name and starting the thread. / comments
Hi,
thank you for the suggestion concerning the thread name. We will take a look if we can change the order of settings the name and starting the thread.
Hil,
here another suggestion (if this has already been discussed I'm sorry):
It would be great if the Thread column would display the thread name if one was set. We name all our threads to identify them in traces an during debugging. / comments
Hil,
here another suggestion (if this has already been discussed I'm sorry):
It would be great if the Thread column would display the thread name if one was set. We name all our threads to identify...
Hi Brian,
sorry for my delayed answer. Now we tried your suggestion:
When we are switshing to fast mode we get proper results in fast mode. When we are switching back to detailed mode, we still get 0 results. / comments
Hi Brian,
sorry for my delayed answer. Now we tried your suggestion:
When we are switshing to fast mode we get proper results in fast mode. When we are switching back to detailed mode, we still get...
Hi Brian,
We are running Windows XP in the idle task of a VxWorks real-time system. We have checked with a monitor program of the VxWorks kernel that the Windows task has >90% of the CPU time. But I think this configuration is like a running Windows in a virtual machine.
Up to know we cannot recognize a pattern what may cause the problem. Our test run is always the same. Yesterday we had a single profiling run with three snapshots. On the first snapshot everything looks fine. On the 2nd and 3rd snapshot we got no proper results.
At first we thought that rebooting the system solves the problem, but this is not true. At the moment we are using the detailed-mode only. Next time we get the failure we try to switch to fast-mode. / comments
Hi Brian,
We are running Windows XP in the idle task of a VxWorks real-time system. We have checked with a monitor program of the VxWorks kernel that the Windows task has >90% of the CPU time. But...