QSocketNotifier Issue

[TheGrimace]

What I think is going on is the following:

I start the transmitting and receiving of information on their respective threads. When I stop, I wait for the QTcpServer and QTcpSocket to stop before I delete their class holders. The event loop is then given control and one extra QSocketNotifier issue is thrown. At this point, my thread is gone and I get an unhandled exception where QObject is attempting to access memory that doesn't belong to it (namely the pointer to the thread).

Edit:

How would I handle the default notifier issues? I am confused as I cannot even find out how to get a pointer to it.

[marcel]

OK. But I still don't understand from where the exception is coming from... From the GUI thread?

About the other thing, getting a handle of the default socket notifier... well, you can't do that.

Regards

[TheGrimace]

All right. I am a little confused. How can I ignore something that I can't point to?

As for the exception:

When looking at the stack trace. It appears that the first call comes from threadex() and propogates through Qt libraries until it reaches the QEventHandler which calls QSocketNotifier which calls the QObject library. Here it tries to return a pointer to a unallocated area of memory.

Thank you for the information you are providing

[marcel]

I do not believe the problem lies in QSocketNotifier. It must be something else.
But, as usually, your descriptions are very vague .

If the worker thread is stopped(and deleted I assume), then why another thread's event dispatcher owns a socket notifier for your dead thread?

The socket notifier for a worker thread should be owned by the thread's event dispatcher.
Perhaps this is another thread problem.

This is as much as I can say(actually, mostly assume) based on your post.

Regards

[TheGrimace]

Well, I am accessing the sockets from another thread for reading and writing. The QSocketNotifier complains about this, but it still works. Afterward, I do not delete the thread that accessed these members, only the one which created them.

I apologize that I am not more clear. I would show code, but as I have stated in other posts: most of the time I am asking about code which belongs to my company and not to me. And they have issues with my posting any part of it. I can, however, try to paint a layout of the objects involved:

GUI
|
\/
Main Thread
|
\/
Another Thread
/ \
\/ \/
TCPServer TCPClient

The QTcpServer and QTcpClients are created in TCPServer and TCPClient respectively. They are accessed from "Another Thread" for reading and writing.

It is a blocking TCP design like Fortune Server Blocking example.

Everything works until I stop. When I stop. I wait for everything to disconnect and then delete TCPServer and TCPClient. and stop the run method of "Another Thread"

After all of this has happened and Qt gets the event loop back, the QSocketNotifier is called by threadex.