Well, i would have thought it's pretty obvious that's not the problem, as (if you'd run the program) when you press 'remote $wait++' the sub stop fires and $wait is incremented... See the output in my original post.

Hmm, my perlport says that too, although i'd have to disagree. I've been sending & trapping signals on win32 for a while now and never noticed any real difference with unix...

Update: perlport last update: v1.48, 02 February 2001 - that might explain it... 

use strict;
$|++;

my @signal = sort grep( $_ ne 'KILL', keys( %SIG ) );
push( @signal, 'KILL' );  # SIGKILL last
print "Signals: ", join( ', ', @signal ), "\n\n";

my $pid;
unless( $pid = fork )
{
  foreach my $type ( @signal )
  {
    $SIG{$type} = sub { print "    SIG$type received!\n" };
  }
  while( 1 ) { sleep 1 }
}

sleep 1;

foreach ( @signal )
{
  print "Sending pid $pid a SIG$_...\n";
  kill( $_, $pid );
  sleep 1;
}

__END__

Signals: ABRT, ALRM, BREAK, CHLD, CLD, CONT, FPE, HUP, ILL, INT, NUM05
+, NUM06, NUM07, NUM10, NUM12, NUM16, NUM17, NUM18, NUM19, NUM24, PIPE
+, QUIT, SEGV, STOP, TERM, KILL

Sending pid -1336 a SIGABRT...
    SIGABRT received!
Sending pid -1336 a SIGALRM...
    SIGALRM received!
Sending pid -1336 a SIGBREAK...
    SIGQUIT received!
Sending pid -1336 a SIGCHLD...
    SIGCLD received!
Sending pid -1336 a SIGCLD...
    SIGCLD received!
Sending pid -1336 a SIGCONT...
    SIGCONT received!
Sending pid -1336 a SIGFPE...
    SIGFPE received!
Sending pid -1336 a SIGHUP...
    SIGHUP received!
Sending pid -1336 a SIGILL...
    SIGILL received!
Sending pid -1336 a SIGINT...
    SIGINT received!
Sending pid -1336 a SIGNUM05...
    SIGNUM05 received!
Sending pid -1336 a SIGNUM06...
    SIGNUM06 received!
Sending pid -1336 a SIGNUM07...
    SIGNUM07 received!
Sending pid -1336 a SIGNUM10...
    SIGNUM10 received!
Sending pid -1336 a SIGNUM12...
    SIGNUM12 received!
Sending pid -1336 a SIGNUM16...
    SIGNUM16 received!
Sending pid -1336 a SIGNUM17...
    SIGNUM17 received!
Sending pid -1336 a SIGNUM18...
    SIGNUM18 received!
Sending pid -1336 a SIGNUM19...
    SIGNUM19 received!
Sending pid -1336 a SIGNUM24...
    SIGNUM24 received!
Sending pid -1336 a SIGPIPE...
    SIGPIPE received!
Sending pid -1336 a SIGQUIT...
    SIGQUIT received!
Sending pid -1336 a SIGSEGV...
    SIGSEGV received!
Sending pid -1336 a SIGSTOP...
    SIGSTOP received!
Sending pid -1336 a SIGTERM...
    SIGTERM received!
Sending pid -1336 a SIGKILL...
(child dies)

[download]

- ><iper 

use japh; print;

[download]

In reply to Re: Re: Re: Re: Tk and waitVariable on tied variables by xiper
in thread Tk and waitVariable on tied variables by Roger

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.