named-pipes

I'm trying to catch debug information from VMware. This might be an easy task because you can redirect all debug information from VMware's OS into the named pipe like is nicely described here . It works fine with WinDbg but I want to create my own application which will do exactly the same. So I've decided to connect to the named pipe provided by VMware and read from it. I'm able to connect to that named pipe but I'm getting meaningless result when reading from the pipe. I've simplified the real code into the unsafe infinite loop. It's enough to have a memo and button on a form and use the

So I've been reading lots about interprocess communication on .Net. Named pipes, remoting. It all seems great but possibly overkill for what I need to do. I want to add a command line interface to my WPF application, so I need a simple IPC mechanism to send the string from one process to the already running app. What does SO recommend for doing so? JP Alioto NamedPipeClientStream and NamedPipeServerStream are pretty simple. Here's a pretty simple example where IPC is used to pass command line arguments from one instance of an application to another. It's not exactly what you want to do, but

I am writing a simple Named Pipes server for Windows, calling the Windows API (in Java with JNA but this is not relevant). I am trying to figure out how to avoid that the server stays stuck forever waiting for a client to connect or for data to come from the client. The server code does the following: 1) It creates the pipe by calling CreateNamedPipe , with PIPE_WAIT in the dwPipeMode argument. 2) It calls ConnectNamedPipe which doesn't return until a client has connected. 3) It enters a loop where it repeatedly reads a message from the client by calling ReadFile which doesn't return until

I need help returning a "status code" from my child program back to the parent, where it will check the status code, print code, and exit the parent. This is for a class project, so I will put some relevant code here, but I don't to post the entire project for obvious reasons. I have forked and created the child process through exec. The parent does some fancy math and uses a named pipe to push data to the child process. The child does some more fancy math. When I uses a keyword, the child needs to return the number of times it did the fancy math on its end back to the parent, where the parent

I'm trying to create an in-process unit test for my service to client interactions using net.pipe binding. Like a good WCF service it uses FaultContractAttribute on service operations to expose possible faults (wrapped exceptions) to metadata. I would like to have the client and service endpoints configured thru XML (App.config). However, whenever a fault is thrown, it's just a CommunicationException "pipe has closed", and not the typed Fault I was expecting. System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). I tried

The WaitNamedPipe function allows a pipe client application to synchronously wait for an available connection on a named pipe server. You then call CreateFile to open the pipe as a client. Pseudocode: // loop works around race condition with WaitNamedPipe and CreateFile HANDLE hPipe; while (true) { if (WaitNamedPipe says connection is ready) { hPipe = CreateFile(...); if (hPipe ok or last error is NOT pipe busy) { break; // hPipe is valid or last error is set } } else { break; // WaitNamedPipe failed } } The problem is that these are all blocking, synchronous calls. What is a good way to do