BSD Portswip/p5-Perl-Unsafe-Signals 0.03 NetBSD
Enable unsafe signal delivery for short periods of time
- System
- NetBSD
- Repository
- pkgsrc-wip
- Maintainer
- [email protected]
- License
- ${PERL5_LICENSE}
- Categories
- wip, devel, perl5
Description
Allows to enable unsafe signal delivery just for a short period of time.
In Perl 5.8.0 the so-called "safe signals" were introduced. This means that Perl no longer handles signals immediately but instead "between opcodes", when it is safe to do so. The earlier immediate handling easily could corrupt the internal state of Perl, resulting in mysterious crashes.
It's possible since perl 5.8.1 to globally disable this feature by using the PERL_SIGNALS environment variables (as specified in perlrun/PERL_SIGNALS); but there's no way to disable it locally, for a short period of time. That's however something you might want to do, if, for example, your Perl program calls a C routine that will potentially run for a long time and for which you want to set a timeout.
This module therefore allows you to define UNSAFE_SIGNALS blocks in which signals will be handled "unsafely".
Note that, no matter how short you make the unsafe block, it will still be unsafe. Use with caution.
In the other systems
The newest version among them is 0.03, as upstream numbers it.
| System | Port | Version | Vulnerabilities | Status | Maintainer | Last update |
|---|---|---|---|---|---|---|
| NetBSD | wip/p5-Perl-Unsafe-Signals | 0.03 newest | none known | - | [email protected] | - |
| FreeBSD | devel/p5-Perl-Unsafe-Signals by name | 0.03 newest | none known | - | [email protected] | - |
| DragonFly | devel/p5-Perl-Unsafe-Signals by name | 0.03 newest | none known | - | [email protected] | - |
| HardenedBSD | devel/p5-Perl-Unsafe-Signals by name | 0.03 newest | no data | - | [email protected] | - |
| GhostBSD | devel/p5-Perl-Unsafe-Signals by name | 0.03 newest | no data | - | [email protected] | - |
Install
From pkgsrc-wip (no binary package):
cd /usr/pkgsrc/wip/p5-Perl-Unsafe-Signals && make install cleanDependency graph
Ports that need it on the left, what it needs to run on the right; at most 8 of each. "Dependencies" below lists them all.