[mythtv] Overlapping calls to readSocket

[Buechler, Mark R]

After 2 hours of running in gdb I received this error before the backend
locked:

QSocketNotifier: Multiple socket notifiers for same socket 23 and type read

The backend still didn't dump, however, it just stopped sending packets and
refused new connections. 

-----Original Message-----
From: Buechler, Mark R [mailto:Mark_R_Buechler at bausch.com] 
Sent: Tuesday, April 12, 2005 7:56 PM
To: 'Development of mythtv'
Subject: [mythtv] Overlapping calls to readSocket

Updated to todays CVS and I see there's been updates to mainserver.cpp.
Since then I'm getting in the log a few "Overlapping calls to readSocket"
messages. Has anyone else seen these? Shortly after these messages appear
the backend dumps. I'm unable to get the backend to dump under gdb which
points to a possible race condition. Was wondering if anyone else has seen
this as well.

- Mark.





EMAIL DISCLAIMER 

Please Note: The information contained in this message may be privileged and
confidential, protected from disclosure, and/or intended only for the use of
the individual or entity named above. If the reader of this message is not
the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
disclosure, distribution, copying or other dissemination of this
communication is strictly prohibited. If you received this communication in
error, please immediately reply to the sender, delete the message and
destroy all copies of it.

Thank You






EMAIL DISCLAIMER 

Please Note: The information contained in this message may be privileged and
confidential, protected from disclosure, and/or intended only for the use of
the individual or entity named above. If the reader of this message is not
the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
disclosure, distribution, copying or other dissemination of this
communication is strictly prohibited. If you received this communication in
error, please immediately reply to the sender, delete the message and
destroy all copies of it.

Thank You