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.
1) Are there any system calls that will give the thread id of the currently running thread?
2) How to make a thread respond to a signal?
I had tried making a simple program where the main program first makes a thread which will print the character‘t’ in the standard output in an infinite loop, and the main program will print the character ‘m’ in the standard output. A signal handler for the signal SIGINT was installed in the main program which will print “You pressed ctrl+c” and will exit. Now, while executing the program, when the main program was executing (printing ‘m’ in the terminal), pressing ctrl+c was caught by the signal handler and printed the desired output. “You pressed ctrl+c” and exited.
But when the thread was executing (printing‘t’ in the terminal), pressing ctrl+c had no effect at all. I tried installing a separate signal handler in the thread by including the ‘signal()’ system call in the function which the thread was executing. Still there was no effect.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
You'd better tell what O/S, kernel and thread implementation you are using.
For example, LinuxThreads is far from being compliant to the POSIX model, you may want to look at the BUGS section of pthread_kill manual page on your system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.