Package: ruby1.8
Version: 1.8.7.302-2
Severity: minor
Hi Lucas et al, a puzzle for you.
Attempting
Kernel.trap("SIGINT", "SIG_DFL")
doesn't actually set the handling of SIGINT to SIG_DFL at all, but
makes the script print a backtrace on interruption.
According to [1], with "SIG_DFL" the operating system's default
handler will be invoked. I would interpret this as meaning the
effect should be analogous to signal(SIGINT, SIG_DFL).
Noticed while debugging apt-listbugs's handling of ^C. [2]
Hints? Is this behavior intended?
Jonathan
[1] http://ruby-doc.org/core/classes/Kernel.html#M005975
[2] http://bugs.debian.org/605039
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
