Ruby: binding.irb in rescue block: Ctrl-C signal works only once
Without binding.irb the following code behaves as expected:
count = 0
loop do
puts count += 1
sleep 1
rescue Interrupt => e
puts "interrupted!"
# binding.irb
next
end
Every stroke of Ctrl-C produces the line "interrupted!".
In contrast to that, the same code with the line binding.irb reacts to the Ctrl-C stroke only once:
count = 0
loop do
puts count += 1
sleep 1
rescue Interrupt => e
puts "interrupted!"
binding.irb
next
end
After exiting irb the subsequent Ctrl-C strokes don't have any effect, not even printing the line "interrupted!".
Why?
ruby exception-handling irb
asked Nov 23 '18 at 12:56
Min-Soo PipefeetMin-Soo Pipefeet
23312
add a comment |
Without binding.irb the following code behaves as expected:
count = 0
loop do
puts count += 1
sleep 1
rescue Interrupt => e
puts "interrupted!"
# binding.irb
next
end
Every stroke of Ctrl-C produces the line "interrupted!".
In contrast to that, the same code with the line binding.irb reacts to the Ctrl-C stroke only once:
count = 0
loop do
puts count += 1
sleep 1
rescue Interrupt => e
puts "interrupted!"
binding.irb
next
end
After exiting irb the subsequent Ctrl-C strokes don't have any effect, not even printing the line "interrupted!".
Why?
ruby exception-handling irb
asked Nov 23 '18 at 12:56
Min-Soo PipefeetMin-Soo Pipefeet
23312
Seems like irb is messing with the signal handler.
– Stefan
Nov 23 '18 at 14:08
add a comment |
Without binding.irb the following code behaves as expected:
count = 0
loop do
puts count += 1
sleep 1
rescue Interrupt => e
puts "interrupted!"
# binding.irb
next
end
Every stroke of Ctrl-C produces the line "interrupted!".
In contrast to that, the same code with the line binding.irb reacts to the Ctrl-C stroke only once:
count = 0
loop do
puts count += 1
sleep 1
rescue Interrupt => e
puts "interrupted!"
binding.irb
next
end
After exiting irb the subsequent Ctrl-C strokes don't have any effect, not even printing the line "interrupted!".
Why?
ruby exception-handling irb
asked Nov 23 '18 at 12:56
Min-Soo PipefeetMin-Soo Pipefeet
23312
Without binding.irb the following code behaves as expected:
count = 0
loop do
puts count += 1
sleep 1
rescue Interrupt => e
puts "interrupted!"
# binding.irb
next
end
Every stroke of Ctrl-C produces the line "interrupted!".
In contrast to that, the same code with the line binding.irb reacts to the Ctrl-C stroke only once:
count = 0
loop do
puts count += 1
sleep 1
rescue Interrupt => e
puts "interrupted!"
binding.irb
next
end
After exiting irb the subsequent Ctrl-C strokes don't have any effect, not even printing the line "interrupted!".
Why?
ruby exception-handling irb
ruby exception-handling irb
asked Nov 23 '18 at 12:56
Min-Soo PipefeetMin-Soo Pipefeet
23312
asked Nov 23 '18 at 12:56
Min-Soo PipefeetMin-Soo Pipefeet
23312
asked Nov 23 '18 at 12:56
Min-Soo PipefeetMin-Soo Pipefeet
23312
asked Nov 23 '18 at 12:56
Min-Soo PipefeetMin-Soo Pipefeet
23312
asked Nov 23 '18 at 12:56
Min-Soo PipefeetMin-Soo Pipefeet
23312
23312
Seems like irb is messing with the signal handler.
– Stefan
Nov 23 '18 at 14:08
add a comment |
Seems like irb is messing with the signal handler.
– Stefan
Nov 23 '18 at 14:08
Seems like irb is messing with the signal handler.
– Stefan
Nov 23 '18 at 14:08
Seems like irb is messing with the signal handler.
– Stefan
Nov 23 '18 at 14:08
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53447150%2fruby-binding-irb-in-rescue-block-ctrl-c-signal-works-only-once%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53447150%2fruby-binding-irb-in-rescue-block-ctrl-c-signal-works-only-once%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Seems like irb is messing with the signal handler.
– Stefan
Nov 23 '18 at 14:08