Skip Menu |

This queue is for tickets about the Sys-SigAction CPAN distribution.

Report information
The Basics
Id: 39946
Status: resolved
Priority: 0/
Queue: Sys-SigAction

Owner: lab [...]
Requestors: krivenok [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

CC: "Lincoln A. Baxter" <lab [...]>, "Lincoln A. Baxter" <lab [...]>
Subject: Sys::SigAction and "safe" attribute.
Date: Fri, 10 Oct 2008 16:44:00 +0400
To: bug-Sys-SigAction [...]
From: "Dmitry V. Krivenok" <krivenok [...]>
Download (untitled) / with headers
text/plain 918b
Hello! Doc ( says that it's possible to pass "safe" attribute in set_sig_handler: my $h = set_sig_handler( 'ALRM' ,\&mysubname ,{ mask=>[ 'ALRM' ] ,safe=>1 } ); However, I found (in version 0.10) that this attribute is ignored (it is just checked in _attrs_warning subroutine). Why not to add $act->safe( $attrs->{safe} ); after my $act = POSIX::SigAction->new( $handler ,$mask ,$attrs->{flags} ); if perl >= 5.8.2 is used? Currently we always use unsafe signals model (despite of safe attribute). Thank you beforehand! -- Sincerely yours, Dmitry V. Krivenok Orange System Company Saint-Petersburg, Russia work phone: +7 812 332-32-40 cellular phone: +7 921 576-70-91 e-mail: web: skype: krivenok_dmitry jabber: icq: 242-526-443
Subject: Sys::SigAction and "safe" attribute. (fixed by Sys::SigAction 0.11
This was a duplicate of ticket #39599. The suggested patch has been applied.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to