11 comments
Comment actions Permalink

So you are going to demonstratively ignore this issue?

0
Comment actions Permalink

Sorry about delayed reply, but the holidays are quite long here.
Fix for your problem with step out has caused another major problem, and turning it back on requires some additional investigation. From what we know RUBY-17214 had a bigger impact on debugger users.

0
Comment actions Permalink
module Mod1
  def self.noop
  end
  def self.foo
    noop
    self
  end

  def self.bar
    noop
    self
  end
end

Mod1.foo.bar


This is a very basic and very common scenario (chained methods).  If  step out does not work here, then it can hardly be said to exist.  I  have not experienced the bugs you linked to, I guess they are not that  universal, neither has clear repro directions, this one does though, it  will affect anyone who actually needs step out.  If you truly can't  accommodate both or until you do, this behavior needs to be user  configurable (env var or some other config)

0
Comment actions Permalink

Because they don't have a clear steps to reproduce doesn't mean they should not be fixed, right? We were able to reproduce that problem using the most basic Rails application. We will take a look at your problem

0
Comment actions Permalink

I did not say they should not be fixed, but that until you can fix them  without breaking "step out" you should make the behavior in question  user configurable.

0
Comment actions Permalink

What is the status of this?  Since this is evidently not a quick fix, can you make this user configurable in the mean time?

0
Comment actions Permalink

Making this configurable will require patching native extension, which is somewhat equivalent to proper fix. You can uninstall latest debase and install version that works for you as a workaround.

0
Comment actions Permalink

Being pinned to an older version is only an adequate workaround if the next release of debase will have a proper fix, is that what you are implying?  Otherwise letting the ide and debase get out of sync seems like a bad idea.

0
Comment actions Permalink

Yes, we're going to fix debase properly, however getting debugger to work correctly may require updating to the latest tiny update of your current ruby version

0
Comment actions Permalink

Are you waiting for a fix in MRI?

0
Comment actions Permalink

Sorry, I've been away for some time.

Current state is this: there's some fix in MRI that may help in case of RUBY-17214, which I need to verify and I'm currently struggling with a reproducible scenario (used to break all the time, now it doesn't). When it's verified to work ok on latest bugfix updates, I'll rollback my fix that caused incorrect stepping 

0

Please sign in to leave a comment.