USING REMOTE TOOLS
You can use the various Compact 7 Remote tools (refer to Chapter 9, “Debug and Remote Tools”) to check on the functionality of a device driver. There is also an API that can facilitate the development of custom tools. Table 34-3 is a summary of the uses of the Remote Tools in driver debugging.
REMOTE TOOL | CHECKS |
File Viewer | That the loaded image has the driver DLL in\Windows. |
Registry Editor | That driver registry settings are in the registry as configured.That the driver is loaded by searching for it under HKLM\Drivers\Active. |
System Information | That the driver is loaded. |
Process Viewer | Can examine the processes running on a system.You can drill into the threads and modules loaded by a process with a view to determining under what process a driver (module) is loaded. |
Kernel Tracker | Useful to examine threads, events, and other synchronization entities, deadlock, interrupts, and so on. |
Performance Monitor | This facilitates looking at performance indicators. You can track such things as kernel time, user time, and memory usage as graphs and tables. Custom metrics can be implemented in code. |
Profiler | This facilitates tracking the time function calls take and determines where most of the system time is consumed and can therefore locate bottlenecks. |
Resource Leak Detector | Memory leaks. |
Get Professional Windows® Embedded Compact 7 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.