continue's behavior is already tested, I think it'll be enough.
class A define_method "method1" do return 1 end def foo method1 # suspect we may stop here instead end end A.new.foo # breakpoint (stops here) puts '1' # after step over should should stop here
var localwould be a way. Another way would be
eval condition, or something like that
Hello @deivid-rodriguez: I believe I found a bug in the latest release. However it is so basic that it leads me to believe it is actually a configuration error on my end. However, I can reproduce the error on fresh installs of latest version 11.1.0, and it is not present for 11.0.1.
So: there is a broken path in inside of core.rb (line 4:
require_relative 'byebug') which errors out when trying to load the file. That makes sense since the byebug folder inside of lib does not contain a
byebug.rb file. The file it is looking for is apparently in the parent directory, however changing the line to
require_relative '../byebug' does not help. Just a little later while loading Byebug's post-mortem settings, I get a seemingly unrelated error:
undefined methodpost_mortem=' for Byebug:Module`
Hi @jorge-barreto! Thanks so much for reporting this early. Could you post steps for me to reproduce the problem? How are you installing byebug? Which OS? Which ruby version? That
require_relative should actually load a
.so file (or whichever extension shared libraries have in your OS) located in the same directory. I suspect your installation is not putting the compiled extension in the same folder but in some place only accesible throught the $LOAD_PATH.
So, I will revert that specific change and use
require again there and release 11.1.1, but if you can help me figure out how this happened and how to prevent it in the future, that'd be awesome.
install_extension_in_libreturns false (as per your link) prevents the
.sofile from being copied to byebug's
libfolder, which is what causes the bug in the first place.