mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
31b2cd38c5
Since enabling YJIT or MJIT drastically changes what could go wrong at
runtime, it's good to be front and center about whether they are enabled
when dumping a crash report. Previously, `RUBY_DESCRIPTION` and the
description printed when crashing can be different when a JIT is on.
Introduce a new internal data global, `rb_dynamic_description`, and set
it to be the same as `RUBY_DESCRIPTION` during initialization; use it
when crashing.
* version.c: Init_ruby_description(): Initialize and use
`rb_dynamic_description`.
* error.c: Change crash reports to use `rb_dynamic_description`.
* ruby.c: Call `Init_ruby_description()` earlier. Slightly more work
for when we exit right after printing the description but that
was deemed acceptable.
* include/ruby/version.h: Talk about how JIT info is not in
`ruby_description`.
* test/-ext-/bug_reporter/test_bug_reporter.rb: Remove handling for
crash description being different from `RUBY_DESCRIPTION`.
* test/ruby/test_rubyoptions.rb: ditto
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
Co-authored-by: Alan Wu <alanwu@ruby-lang.org>
|
||
|---|---|---|
| .. | ||
| arith_seq | ||
| array | ||
| bignum | ||
| bug_reporter | ||
| class | ||
| debug | ||
| exception | ||
| file | ||
| float | ||
| funcall | ||
| gvl | ||
| hash | ||
| integer | ||
| iseq_load | ||
| iter | ||
| load | ||
| marshal | ||
| method | ||
| num2int | ||
| path_to_class | ||
| popen_deadlock | ||
| postponed_job | ||
| proc | ||
| rational | ||
| st | ||
| string | ||
| struct | ||
| symbol | ||
| thread | ||
| thread_fd | ||
| time | ||
| tracepoint | ||
| typeddata | ||
| vm | ||
| wait | ||
| win32 | ||
| test_abi.rb | ||
| test_bug-3571.rb | ||
| test_bug-5832.rb | ||
| test_bug-14834.rb | ||
| test_enumerator_kw.rb | ||
| test_notimplement.rb | ||
| test_printf.rb | ||
| test_random.rb | ||
| test_recursion.rb | ||
| test_scan_args.rb | ||