On Jan 16, 2008 8:23 AM, Diego . <[EMAIL PROTECTED]> wrote:
> yes, make test reports all tests passed when compiling 5.8.8 on both (
> fedora 4 and 6 ) but when i compible 5.6.2 on fedora 6 y get some
> errors on test but threads works fine even with some tests failed.
Well, "works fine" is good for so long as it lasts. Still, I wonder:
How do you know your Perl programs do what they should, when you know
your perl binary doesn't do what it should? Could the test that failed
have been trying to do the same thing that you're having trouble
doing?
In any case, your original trouble was that SIGTERM wasn't being
recognized as a signal. How were you using it?
If you're still having trouble with SIGTERM, check out the diagnostic
program I've appended to this message. Do your various perl binaries
say anything interesting when you have them run it?
Hope this helps!
--Tom Phoenix
Stonehenge Perl Training
#!/usr/bin/perl
use strict;
use warnings;
use Config;
my @names = qw{
SIGTERM SIGZERO SIGMUNDFREUD SIGWINCH
SIGCHLD SIGCHILD SIGNAGE SIGUSR1 SIGSEGV
SIGSTOP SIG INT HUP ZERO HALT QUIT
sigterm hup 42 7 -9 3.14159 2001 90210
};
my(@good, @bad);
for my $signame (@names) {
if (eval { kill $signame; 1 }) {
push @good, $signame;
} else {
push @bad, $signame;
}
}
print "These seem to be usable signals: @good\n\n";
print "These are bad signals: @bad\n\n";
print "Perl version: $]\n";
print "Config's list of signals: $Config{sig_name}\n\n";
__END__
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
