sandor
25th June 2011, 20:00
Hello There,
I have a bit of a problem with the signal queue and do hope that someone might give me a hint. There are two threads communicating with each other by emitting signals - works for the other on an existing QTcpSocket connection (it is an API implementation) and signals the other thread when sending and receiving of data was done - the decoded data is available.
The problem is that signals look to be lost after a while, so signals emitted are never received in the thread handling the API via the QTcpSocket. I am looking for a way to debug it - I would like to see why the emitted signal does not arrive. It looks to be random how many times the emitted signal is actually received: sometime only 3x, sometimes much more before it actually gets stuck so emit is done (I see from the log file) but the slot is never triggered - same class, same thread, same instance does it many times before.
Thanks,
Sandor
I have a bit of a problem with the signal queue and do hope that someone might give me a hint. There are two threads communicating with each other by emitting signals - works for the other on an existing QTcpSocket connection (it is an API implementation) and signals the other thread when sending and receiving of data was done - the decoded data is available.
The problem is that signals look to be lost after a while, so signals emitted are never received in the thread handling the API via the QTcpSocket. I am looking for a way to debug it - I would like to see why the emitted signal does not arrive. It looks to be random how many times the emitted signal is actually received: sometime only 3x, sometimes much more before it actually gets stuck so emit is done (I see from the log file) but the slot is never triggered - same class, same thread, same instance does it many times before.
Thanks,
Sandor