The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
BugTraq+ Release Management Values
COMMIT TO FIX:
y.s.ramakrishna@eng 2000-10-23: Sounds like a good idea.
How does it work for Windows? (similar sigaction-like interface?)>
y.s.ramakrishna@eng 2001-01-29: Mingyao Yang has a prototype that addresses
this issue. It's currently being reviewed for integration at a future date.
Making Mingyao the RE, since he's doing all the work.
Signal-chaining will do two things:
(1) saves preinstalled user signal handlers when installing our own signal
handlers for some signals used by the vm (mostly some synchronous
(2) disallows the installation of user signal handlers for vm-used signals,
instead, saves those user signals handlers. This is done by linking a .so
file with user's main program, or preloading the .so file with
LD_PRELOAD. The .so file interposes those os calls that install signal
for Solaris/Linux, sigaction, signal, sigset
For both (1) and (2), during signal handling by the vm, if the signal is not
for the vm to handle, the saved user signal handler will be invoked.