SimpleIPCServer crashing on OSX

[Josh]

Hi
I have a strange problem.
I have a application that can receive instruction from console app, this works well in windows 32/64bit.

On mac, when I run the 'server' app crashes with : raised exception class :'EInOutError\x10' with message Invalid File Handle.

I have traced the error to IPCSErver.Message procedure.

The Code I have that read the message in a timer is

Code: Pascal  [Select][+][-]

1. if ((my_ipcserver_running=true) and (My_IPCServer.Active) and (My_App_Started)) then
2. begin
3.   If  My_IPCServer.PeekMessage(2,false) then
4.   begin
5.      My_IPCServer.ReadMessage;   <-- This is what fires the error.
6.   end;
7. end;
8.  

I am wondering if the IPCServer is usig temp files for messages; if it is; is it likely that you will not be able to run from within a bundle.

Has anyone else had a similar problem.

Josh

[lucamar]

It uses a file (a FIFO named pipe), but it's created in the temp dir. From {fpc_source}/packages/fcl-process/src/unix/simpleipc.inc

Code: Pascal  [Select][+][-]

1. constructor TPipeServerComm.Create(AOWner: TSimpleIPCServer);
2. begin
3.   inherited Create(AOWner);
4.   FFileName:=Owner.ServerID;
5.   If Not Owner.Global then
6.     FFileName:=FFileName+'-'+IntToStr(fpGetPID);
7.   if FFileName[1]<>'/' then
8.     FFileName:=GetTempDir(Owner.Global)+FFileName;
9. end;
10.  
11. procedure TPipeServerComm.StartServer;
12.  
13. const
14.   PrivateRights = S_IRUSR or S_IWUSR;
15.   GlobalRights  = PrivateRights or S_IRGRP or S_IWGRP or S_IROTH or S_IWOTH;
16.   Rights : Array [Boolean] of Integer = (PrivateRights,GlobalRights);  
17.    
18. begin
19.   If not FileExists(FFileName) then
20.     If (fpmkFifo(FFileName,438)<>0) then
21.       DoError(SErrFailedToCreatePipe,[FFileName]);
22.   FStream:=TFileStream.Create(FFileName,fmOpenReadWrite+fmShareDenyNone,Rights[Owner.Global]);
23. end;

I don't how that translates to MacOS, though.

[Josh]

Hi

Thanks for your reply.

I restarted my mac, re-build lazarus and all seems to be working now.

Not sure which one fixed it, I suspect re-sarting the mac though, as other apps seems more responsive.