ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If that does not work, then try designing your s/w such that you can notify the thread via some other means (ie setting a semaphore or other data type).
Here after cancel the thread, i delete the object passing to the thread function. Then I am getting crash because it is used by thread function after cancel the function also.
Please help me to solve this problem in another way.
Here after cancel the thread, i delete the object passing to the thread function. Then I am getting crash because it is used by thread function after cancel the function also.
Please help me to solve this problem in another way.
Regards,
Nagendra R
Ok, wait for a moment while I put on my ESP-enhancing hat, so that I can visualize your code....
Of course it doesn't. You have opened a can containing more worms than one can possibly imagine. That is a cute way of saying there are many, many potential problems raised by asynchronous canceling of a thread. You're lucky that the program consistently fails. A much worse situation would be if the program ran most of the time, but failed only occasionally. This can easily happen with POSIX threads.
To understand why all this is true, you should run (not walk) to your nearest bookseller and buy David R. Butenhof's excellent book Programming with POSIX Threads, published by Addison Wesley. (The copy I have of a similar book published by O'Reilly looks complete, but is sufficiently incomplete as to be dangerous.)
When you have read this book, you may find it easier simply to rewrite your code so that the thread that is to be canceled somehow finds out about this desire, and terminates by itself, gracefully.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.