It does sound like resource contention - the
(void)cTelnet::handle_socket_signal_readyRead() is a SLOT connected to
the (QTcpSocket) cTelnet::socket and that WILL be called by the
asynchronous thread that Qt uses for networking - we may need to add
some QMutex stuff to protect resources that that m
Humm, (std::basic_string) cTelnet::mMudData looks a bit suspect - we
read and write to that all over the cTelnet class and I do not know
enough to say whether that is safe - also it is not a Qt type so does
not have the same built in protections that Qt now builds into things
like QString for threa
2 matches
Mail list logo
