Target Device Rebooting (Windows CE 5.0)

Send Feedback

On a target device, the shared memory segment for Remote Call Profiler is released only after all profiled applications quit.

The memory segment can only be released by an application run from the Remote Call Profiler Collection Control window. For information about the Collection Control window, see Remote Call Profiler Collection Control Window.

If you want to collect data, but a profiled application from a previous session of data collection fails to free associated memory, you must reboot the target device before starting data collection.

You must reboot the target device after a profiling run if any of the following conditions are met:

  • Instrumented code continues to run on the target device after you choose Finish or Cancel in the Collection Control window.
  • Instrumented code continues to run on the target device in a process not initiated by Remote Call Profiler (for example, a process that is run by the Run Programs command on the Target menu of the Platform Builder IDE).
  • There is an error while collecting data (for example, a loss of connection to the target device). In this situation, close the Remote Call Profiler window and use Task Manager to end the CePubSub.exe process.

See Also

Code Profiling

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.