Destroying a global object

Question

1.00/5 (1 vote)

See more:

, +

I have a global object which is shared by different threads. To provide the synchronization, I have added a mutex inside the global object.
Mutex will be locked by a thread before accessing the data inside the object.
Everything is fine except delete.
If a thread is locking the mutex and deleting the object.
How again it can unlock it?

How can a safe delete be implemented using this approach i.e. keeping mutex inside the object?

What I have tried:

I am not sure what can be solution.

Posted 27-Mar-17 21:18pm

Chandan_srivastava

Updated 27-Mar-17 21:37pm

Add a Solution

1 solution

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 · 2017-03-27T21:37:00

Solution 1

Why should a thread delete a global object?

Objects should be only deleted by the owning thread. With global objects this is probably the main thread.

Because it contains a mutex, there should be no need to delete the object. Just let it exist during the lifetime of the application.

If you want to pass dynamic data between threads, the mutex should not be part of the object holding the data.

Posted 27-Mar-17 21:37pm

Jochen Arndt

Comments

Chandan_srivastava 28-Mar-17 6:54am

I can't keep the data for the life time of the application. I have dynamic data which should be shared among threads. For synchronization, I am using mutex which is part of the data. If any thread wants to access the data, first it has to acquire the mutex.
By this way I am providing mutual exclusion. But at some point data needs to be deleted and there problem comes.

Jochen Arndt 28-Mar-17 7:12am

But you must keep the mutex.

Just move it out of the data object (you can still have a reference to it in the object). Then you have two globals:
The mutex and a pointer to a dynamic object.

Use the mutex to control access to the object which includes creation, modification, and deletion.

Or better, create a class containing the mutex and the dynamic object that provides all the required functions. The mutex can be static (for all instances of the class) or not (one mutex for each instance).

Chandan_srivastava 28-Mar-17 10:03am

Thanks Jochen. With this approach, I need to do management of those externally created mutexs for the data objects.