Re: Signals and threads

shibu-kundara wrote:
Hi

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 .


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???

You're messing with a system library - don't do that unless you
know exactly what you're doing. Other parts of the library might (and does) rely on a particular behavior.
.

Relevant Pages

  • Re: Signals and threads
    ... In the pthread_library clone call is used, In the man page of clone ... the signal handlers will not be shared ... Inspite of all this the last sig handler function is getting called ...
    (comp.os.linux.embedded)
  • Re: Signals and threads
    ... In the pthread_library clone call is used, In the man page of clone ... the signal handlers will not be shared ... Inspite of all this the last sig handler function is getting called ...
    (comp.os.linux.development.apps)
  • Re: Signals and threads
    ... the signal handlers will not be shared ... thread modifies and install a new handler in this already allocated ... Inspite of all this the last sig handler function is getting called ... when i send the signal to the first thread. ...
    (comp.os.linux.development.apps)
  • Re: Zombie Trouble Shooting
    ... my $handler = sub { ... # do something with $pid ... The reason is that old SysV machines are broken wrt signal handlers ...
    (perl.beginners)