What exactly does this mean — “Maybe IRB bug!”? What does that tell me about the potential root cause of an exception?
Note that the text “Maybe IRB bug!!” was printed after the stack trace as part of the exception output.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What exactly does this mean — “Maybe IRB bug!”? What does that tell me about the potential root cause of an exception?
Note that the text “Maybe IRB bug!!” was printed after the stack trace as part of the exception output.
This message means that IRB detected the cause of the stack trace being inside IRB’s own code, not in the code you entered to be executed. And depending on what you did before that, it is thus likely that you triggered a bug in IRB.
A stack trace or segfault of a tool itself (as opposed to an error in user-code) is considered a bug almost all of the time. A tool should never die on user data, but always fail gracefully and with meaningful error messages. The one you see here is an attempt for one of those 🙂