You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
step command can step into Ruby's prelude methods, like binding.irb.
rdbg -e 's' test.rb
[1, 3] in test.rb
=> 1| binding.irb
2|
3| a = 1
=>#0 <main> at test.rb:1
(rdbg:commands) s
# No sourcefile available for <internal:prelude>
=>#0 Binding#irb at <internal:prelude>:19
#1 <main> at test.rb:1
(rdbg)
For the `<internal:...>` files does not have a file and `absolute_path`
is nil, so it is assumed as eval'ed code and `skip_location?` add prefix
`!eval:` to the path name. So it also cheks with this prefix too.
fix#866
For the `<internal:...>` files does not have a file and `absolute_path`
is nil, so it is assumed as eval'ed code and `skip_location?` add prefix
`!eval:` to the path name. So it also cheks with this prefix too.
fix#866
Your environment
ruby -v
:1.7.0
rdbg -v
:3.1.2
Describe the bug
step
command can step into Ruby's prelude methods, likebinding.irb
.But looking at the code, it should be skipped by
skip_internal_path?
.To Reproduce
Expected behavior
It shouldn't step into the prelude method but directly into IRB's internal.
Additional context
This is because
skip_location?
appends!eval:
to the frame path, sopath.start_with?('<internal:')
failed to match it.The text was updated successfully, but these errors were encountered: