-
-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backtrace set with set_backtrace is not dup'd properly in 9.2.7.0 #5738
Milestone
Comments
Nice find! Maybe I don't want to know how you found it... |
Thanks, @headius! |
eregon
pushed a commit
to ruby/spec
that referenced
this issue
May 28, 2019
mvz
added a commit
to cucumber/aruba
that referenced
this issue
Jun 12, 2019
There's an issue with dup-ing an exception after its backtrace has been set manually in JRuby 9.2.7.0. It should be resolved in 9.2.8.0 once that's released. See jruby/jruby#5738 for more details.
mvz
added a commit
to cucumber/aruba
that referenced
this issue
Jun 15, 2019
There's an issue with dup-ing an exception after its backtrace has been set manually in JRuby 9.2.7.0. It should be resolved in 9.2.8.0 once that's released. See jruby/jruby#5738 for more details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
jruby -v
:jruby 9.2.7.0 (2.5.3) 2019-04-09 8a269e3 OpenJDK 64-Bit Server VM 11.0.4+2-Debian-1 on 11.0.4+2-Debian-1 [linux-x86_64]
--dev
uname -a
):Linux bean 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux
Expected Behavior
Given the following ruby code:
In MRI and JRuby 9.2.6.0, this prints:
Actual Behavior
In JRuby 9.2.7.0, this prints:
The text was updated successfully, but these errors were encountered: