🚀 go-pugleaf

Greetings all,

I'm trying to debug a recalcitrant C++Builder 6 app and had the
 brainstorm of writing a separate pipe server task to receive/ 
log-to-file debug messages from it. Both programs would reside 
on the same machine. I've tested the pipe server with a small 
console based client app that successfully writes large amounts 
of data, FAST. All appears fine on the server side. (The server 
app is written in the "old-fashioned" WIN32 manner, as I'm that 
kind of guy.)

I blithely thought that incorporating the client side into the 
buggy app would be a snap, but... I can only perform a single 
write into the pipe, using WriteFile(...) before it seems that I 
never get another I/O event signalling that the write was 
finished and the API is ready for another message. 


Here's what the client send routine looks like...the setup of 
the OVERLAPPED struct and creation of the event and existing 
pipe file are done elsewhere. I tried to duplicate the logic of 
the test client.


void TMyAppForm::WriteToPipe(char *pC)
{
     unsigned long BytesWritten;
   
     while(WaitForSingleObject(io.hEvent, 0) == WAIT_TIMEOUT)
           Application->ProcessMessages();

     ResetEvent(io.hEvent);
     if(!WriteFile(hPipe, pC, strlen(pC), &BytesWritten, &io))
     {
         while(GetLastError() == ERROR_IO_PENDING)
               Application->ProcessMessages();
     }
}

Note that I'm a newbie to pipe IPC and am more familiar with M$ 
compiler environments.


Could the main message handler be "eating" my io events? I'm 
stumped.


Thanks for any and all help,


Duane