no sigchild under win32 ?

[Anonymous Monk]

is there no signal send to the father process when a child dies under win32? i created a callback (at least i think i did) but it seems not to work :

$SIG{CHLD} = \&dead_child;

sub dead_child{

       #do what is to be done

}

[gumby]

Does your sub look like this?

sub dead_child {
  ...
  $SIG{CHLD} = \&dead_child;
}
$SIG{CHLD} = \&dead_child;

Upate: At the moment, what does your sub do?

[Anonymous Monk]

no i dont have another callbak in the sub - why? do i need that?

[gumby]

Yes, you need to reinstate the handler. Read the perlipc man page.

[Anonymous Monk]

concerning your updated question: it resets the status_field of my tk-frontend and opens the result-window

[Anonymous Monk]

perhaps it because i didnt use fork() or open() or something like that to create the childprocess but Win32::Process::Create ?

so is there a signal send or another way to know if such a process is trerminated ?

[gumby]

The $SIG{CHLD} handler will not trap anything if you use Win32::Process. :-(

[NaSe77]

why cant i just do something like

END{
    kill(SIGCHLD,$_parent);
}

in the child or so? in fact i tried this but i i got :

Your vendor has not defined POSIX macro SIGCHILD, used at $scriptname 
+line $line

and since my english is not too good i dont realy get what this means and what i should do

[particle]

try Win32::Event. i have an example of usage at my follow-up to my own node at ALRMing behavior on Win32. btw, read perlfaq5 for important info on signals and win32.

~Particle *accelerates*