mirror of
https://github.com/ruby/ruby.git
synced 2025-08-23 13:04:13 +02:00
d592ddd5e6
This caused an issue when `defined?` was in the `if` condition. Its
instructions weren't appended to the instruction sequence even though it was compiled
if a compile-time known logical short-circuit happened before the `defined?`. The catch table
entry (`defined?` compilation produces a catch table entry) was still on the iseq even though the
instructions weren't there. This caused faulty exception handling in the method.
The solution is to no add the catch table entry for `defined?` after a compile-time known logical
short circuit.
This shouldn't touch much code, it's only for cases like the following,
which can occur during debugging:
if false && defined?(Some::CONSTANT)
"more code..."
end
Fixes [Bug #20501]
|
||
|---|---|---|
| .. | ||
| -test- | ||
| test | ||
| _tmpdir.rb | ||
| bundled_gem.rb | ||
| colorize.rb | ||
| core_assertions.rb | ||
| envutil.rb | ||
| find_executable.rb | ||
| gc_checker.rb | ||
| iseq_loader_checker.rb | ||
| jisx0208.rb | ||
| launchable.rb | ||
| leakchecker.rb | ||
| memory_status.rb | ||
| output.rb | ||
| path.rb | ||
| profile_test_all.rb | ||
| tracepointchecker.rb | ||
| vcs.rb | ||
| vpath.rb | ||
| zombie_hunter.rb | ||