Windows Named Pipe Monitor
| Requires: |  org.jancy.io.devmon |
| OS: | Windows |
Under Microsoft Windows, applications, services and drivers often perform IPC (inter-process communication) using named pipes and anonymous pipes. The problem is, there are no well-known tools to sniff/monitor Windows pipe communications, making it rather difficult to debug. The Pipe Monitor plugin is the missing piece of the puzzle - it lets you see what is flowing through Windows named pipes and anonymous pipes.
Since in Windows there are many pipes performing communications at the same time, you need to somehow filter only the pipes you are interested in. Pipe Monitor plugins lets you do just that by specifing a pipe name wildcard - you will only see the data flowing through the pipes with matching names.
Device Monitor Service
The key component of monitors (such as Serial Monitor, Pipe Monitor, etc) is the Device Monitor service. This service consists of a kernel-mode module intercepting requests from applications to the specified devices and a user-mode configuration utility.
Installation and proper configuration of the Device Monitor service is a stumbling point for many users. Please follow these KB (knowledge base) articles for more information:
Gallery
