Feature Requests item #3308168, was opened at 2011-05-26 18:16
Message generated for change (Tracker Item Submitted) made by marshallch
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350612&aid=3308168&group_id=612
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Chris Marshall (marshallch)
Assigned to: Nobody/Anonymous (nobody)
Summary: Update perldl/pdl signal handling for "safe signals"
Initial Comment:
In perl versions since 5.8.x the support for signals has changed
to so called "safe signals" where signals are processed only at
times that are safe for the interpreter and program state.
This has the effect of modifying the receipt of signals by
a program such as the PDL interactive shells perldl and
the new pdl2. Signals can be ignored or received in a
delayed fashion. I also see much more varied behavior
between cygwin perl and activestate perl with the new
signals.
We need to update the code catching Ctrl-C for the
PDL shells so that they are caught as expected (the
old way) in order to allow the desired usage to
interrupt long-running commands or to break out
of a command entry, etc.
I suggest replacing the $SIG{INT} handler code
by corresponding POSIX::sigaction code. Until
that happens, setting PERL_SIGNALS environment
variable to "unsafe" will set all signal handling to
the pre-5.8.x method.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350612&aid=3308168&group_id=612
_______________________________________________
PDL-porters mailing list
PDL-porters@jach.hawaii.edu
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters
