Issue with stepping in VSCode with debase versions 0.2.4 and 0.2.3

[ruby-debug]

Issue with stepping in VSCode with debase versions 0.2.4 and 0.2.3

[ViugiNick]

@mskogen @m-dwyer @jvilk-stripe @erichmusick-stripe Finally reproduced and fixes. Will release a new version ASAP

[mskogen]

You did it! Fixed on my machine now too @ViugiNick

[ViugiNick]

@mskogen Could you please attach an example code snippet, so I can reproduce the problem with stepping

[mskogen]

It isn't anything crazy, this is just a test script I was using to try and step line-by-line. This is how I was troubleshooting the debugging:

puts 4
puts 7
puts 9
puts 3
puts 9
l = 7
puts "hello"
h = 9
puts h + l

[ViugiNick]

@mskogen Thats strange, in RubyMine 2019.2 with 0.2.4 everything works fine

[ViugiNick]

@mskogen breakpoint on the first line and step over all lines

[mskogen]

@ViugiNick I think the issue is with VS Code and the gem. Have you tried reproducing the issue in VS Code?

[ViugiNick]

@mskogen not yet

[ViugiNick]

@mskogen With ruby 2.6.3 everything works fine at least on this sample

[mskogen]

@ViugiNick is this your ruby version?

ruby -v
ruby 2.6.3p62 (2019-04-16 revision 67580) [x64-mingw32]

[mskogen]

Also are you running Windows 10?

[ViugiNick]

@mskogen ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]
running on ubuntu

[mskogen]

@ViugiNick I wonder if this issue is only apparent on the Windows 10 ruby/VS Code configuration? Do you have an easy way to test that? If not I can try to to test on a linux VM as well and see if I can reproduce the same issue.

[ViugiNick]

@mskogen Ok, I'll try to check it on Windows, but could you also test in Linux?

[mskogen]

@ViugiNick ill try to check it out on Linux as well

[erichmusick-stripe]

I can repro the step behavior issue under VS Code 1.36.1 on OSX 10.14.5 using @mskogen 's sample program.

ruby 2.4.5p335 (2018-10-18 revision 65137) [x86_64-darwin18]
ruby-debug-ide 0.6.1
debase 0.2.4

Step behavior works properly when using debase 0.2.2 and 0.2.3.

Not only does stepping fail in 0.2.4, but if I set two breakpoints, hit the first, and hit Continue, the program skips the second breakpoint and then exits.

[jvilk-stripe]

@ViugiNick any luck reproducing? This is a recurring problem for folks with @erichmusick-stripe's setup.

[jvilk-stripe]

@mskogen With Ruby 2.6.4 and Debase 0.2.4, this problem is gone.

There was a bug in Ruby 2.6 where Ruby was not emitting a trace point for some return statements.

See deivid-rodriguez/byebug#550 (comment) for further context.

[ViugiNick]

@jvilk-stripe thanks for pointing this out! @erichmusick-stripe @mskogen Could you check if upgrading ruby resolves the issue?

[m-dwyer]

I've replicated it with @mskogen's sample script above.
Arch Linux, kernel 5.2.11

$ code --version
1.37.1
$ ruby -v
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]
$ gem list | grep -E '(debase|ruby-debug-ide)'
debase (0.2.3)
debase-ruby_core_source (0.10.5)
ruby-debug-ide (0.7.0)

Breakpoints work on the puts, but when trying to step over/into the assignments, the script runs until the end. debase 0.2.4 allows me to hit the first breakpoint, but subsequent breakpoints fail.

With ruby 2.6.4 and debase 0.2.4, the same issue occurs -- I can hit the first breakpoint, but that is all.

EDIT: downgrading to debase 0.2.3beta5 also resolves the issue for me.

[mskogen]

@ViugiNick upgrading Ruby does not fix the issue

[ViugiNick]

@mskogen @m-dwyer @jvilk-stripe I still can't reproduce it, but I added some more logging there: could you please uninstall 0.2.4 debase and install the version from this branch https://github.com/ViugiNick/debase/tree/logging

And attach lines with something like context->... here

[mskogen]

When you try to replicate the issue what version of VisualStudio, Ruby, and debase are you using? Also are you trying to replicate the issue on Windows? @ViugiNick

[ViugiNick]

@mskogen @m-dwyer @jvilk-stripe @erichmusick-stripe 0.2.5 released!

[ViugiNick]

@mskogen @m-dwyer @jvilk-stripe @erichmusick-stripe used to remove 0.2.5 and publich 0.2.4.1 instead (fix included)

[amilano]

Hi everybody... 0.2.5 was removed, but bundler keeps trying to fetch that version instead of 0.2.4.1 is there anything else to do other than manually restricting debase to use a gem lower than 0.2.5?

Even after removing it from the Gemfile, bundling and adding it back bundler keeps looking for 0.2.5

[ViugiNick]

@amilano Maybe that's because of the Gemfile.lock?

[amilano]

Well, I actually removed the gem from Gemfile and bundled in order to delete it from Gemfile.lock... added it again (gem 'debase', '~> 0.2.2') and bundled. Bundler got again 0.2.5 into Gemfile.lock.

For now I restricted the gem to use versions lower to 0.2.5 like this: gem 'debase', '~> 0.2.2', '< 0.2.5'. But I was wondering if there's something else to do, or if it's only me having this issue.