comment on

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks