Details
-
Bug
-
Resolution: Won't Do
-
Not Evaluated
-
None
-
4.8.7
-
None
Description
For the following QLocalSocket scenario on linux:
On the single process:
1) Create QLocalServer, connect to server, write bytes to the socket (do not wait for bytes to be written)
2) Then wait for newConnection() signal on the QLocalServer (using processEvents())
3) Once the signal arrives call waitForReadyRead()
This will timeout since it's possible that events which need to be processed so that data are available for read on the socket are not called. However this is not correct since the method should allow the actual data to be fetched to socket and made it to be ready for read. This should be apparent from the code. On Windows this works correctly.