Re: Signals and threads
- From: loic-dev@xxxxxxx
- Date: 24 Nov 2006 04:37:52 -0800
Hello,
In the pthread_library clone call is used , In the man page of clone
its given that
if CLONE_SIGHAND is not defined, the signal handlers will not be shared
between threads.
I recompiled the pthread library with out CLONE_SIGHAND .
yes... clone() allows you to fine tune what's shared between kernel
schedulable entity... But doing so, you don't get a "Pthread library"
anymore.
I linked the program with the new library , It has been ok in the
do_fork call in the pthread funciton, A new struct of task_struct->sig
is allocated. Also i have seen that the sigaction function call in the
thread modifies and install a new handler in this already allocated
task_struct->sig structure.
Inspite of all this the last sig handler function is getting called
when i send the signal to the first thread. Any clue???
As mentionned by Nils, it is not a good idea at all to change the
Pthreads library behavior. If other programs use it, they will
certainly break in strange way...
Again, the questions you should answer is why do you need that
functionality in first place... And if you do, then create your
seperate "thread" library...
Finally, how do you send the SIGUSR1 to your threadA?
Cheers,
Loic.
.
- Follow-Ups:
- Re: Signals and threads
- From: shibu-kundara
- Re: Signals and threads
- From: shibu-kundara
- Re: Signals and threads
- References:
- Signals and threads
- From: shibu-kundara
- Re: Signals and threads
- From: loic-dev
- Re: Signals and threads
- From: shibu-kundara
- Signals and threads
- Prev by Date: Re: Looking for a extensible shell for debug purpose
- Next by Date: Re: Signals and threads
- Previous by thread: Re: Signals and threads
- Next by thread: Re: Signals and threads
- Index(es):
Relevant Pages
|