If you want to control every process under the CE, threading CPU usage, or you want to know what each thread is the moment at the creation module, the current call stack thread, or you want to know that applications for a period of time after the operation of the reactor process use, the distribution of fragments of memory, and so on, this tool can give you the intuitive answer.
Windows CE Remote Process Explorer (after short CE Process Explorer) is a Mark Russinovich and the Process Explorer similar tools, it only applied to Windows CE system. CE Process Explorer through Platform Manager and Windows CE device establish a connection, as its name would suggest, and the Windows CE Remote File Viewer, CE Process Explorer is a Remote tool. Its terminal operations in the host PC, via TCP / IP, and other transmission media and communications terminal device to reveal when the Windows CE operating system state. Mark Process Explorer and the different focus, CE Process Explorer WinCE platform for the development of the design staff, to focus more on the internal system data revealed.
The current CE Process Explorer support ARM and X86 (including emulator) architecture, MIPS and SH4 framework I have not used the time being not support it. Support the goal of operating systems including Windows CE 4.x/5.0 on Windows CE 6.0 support are also being considered.
As shown below, similar to the Process Explorer, the main interface View from the upper and lower two components. Process view shows that the above list, the following view can display the currently selected Process Thread, Dll, Handle, Window, or Memory Heap information. View each have corresponding context menu, for example, in view of the process you can kill a process, thread View can view a thread in the current call stack.
1, Process View. Light-blue background of the process of non-ROM modules.
2, Thread View. Light-blue background of the main threads thread. Thread View can be seen in each module which thread is created, this diagnosis of the problem is very helpful.
3, Handle View.
4, DLL View. DLL yellow background for the re-positioning of the DLL.
5, Window View. Light blue background window for the top window.
5, Heap View. Light blue background free memory block.
7, Memory View. In Memory View you can see the whole system virtual memory layout, you can find what is the Image File mapping, Thread Stack, Heap in any place where DLL loading and so on.
Some features (Highlights)
1, show that thread call stack (call stack). This is my favorite one of the functions. It can be arbitrary in the operation showed that the call stack thread, the thread observe the work of the state. In a debug symbol circumstances, directly to the source line position.
2, the process of application stack view. Allows you to observe the moment of the application stack usage, as part of the red debris.
3, positioning abnormal address (Crash Finder). Application crashes are common, this feature allows you to the address from the abnormal positioning directly to the source line.