Debug assertion failed...

Question

0.00/5 (No votes)

See more:

C#

THREADSTRUCT* ts = (THREADSTRUCT*)param;



ts->_this->OnInitDialog();

Here OnInitDialog() in in main thread and i am trying to call this method from the child thread(worker thread) which i have created. when i am trying to do this i am getting a debug assertion failed error(Both in Debug mode and release mode).
** I am using Microsoft Visualc++ 6.0 IDE**

Posted 21-Jun-15 21:49pm

Member 11648410

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jochen Arndt · Answer 1 · 2015-06-21T22:15:00

MFC objects are not thread safe. So you can't call MFC functions like OnInitDialog from another thread.

A usual solution to this problem is posting user defined messages from the worker thread to the other (main) thread.

As a starting point you may read Multithreading: Programming Tips[^] and follow the links. This has not changed much since VC 6. But you should think about using a more recent version.

nv3 · Answer 2 · 2015-06-21T22:50:00

This is less a problem of thread-safeness. MFC keeps a map of window handles to MFC objects, which is used to route an incoming windows message to the corresponding C++ class object. This map is thread-specific and can only be accessed from the thread in which the window was created. Hence, you may only deal with windows and controls from the thread that created them. A common technique is to use a single thread for all UI activities and worker threads for all non-UI activities.

That is also the reason why you must specify in MFC whether you want to create a UI or worker thread.

Debug assertion failed...

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0