I wrote sample code of thread control using signaling as advised by monks. As below, but the thread didn't exit when Ctrl+c pressed:
#/usr/bin/perl -w
use strict;
use warnings;
use threads;
use threads::shared;
my @thrList;
my $count=1;
share $count;
$SIG{INT} = \&catch_CtrlC;
&main;
sub main
{
my $counter = 3;
while($counter)
{
$counter--;
my $thrHandle = threads->create(\&thrdfun);
push @thrList, $thrHandle;
}
print " waiting \n";
foreach(@thrList){
$_->join();
}
}
sub thrdfun
{
$SIG{INT} = \&trExit;
print "thrdfun: $count \n";
$count++;
while(1){
}
exit;
}
sub trExit
{
print " exit \n";
threads->exit();
}
sub catch_CtrlC
{
print " catch_CtrlC \n";
foreach(@thrList){
$_->kill("INT");
}
exit;
}
In my plan, catch_CtrlC will first receive the signal and forward it to all thread one by one. For every thread, the trExit will do sth. and exit.
I guess I'm using in a wrong way, righ?
-
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.
|