Ancestors

Written by Steven Harman on 2024-10-14 at 20:39

Looking for help moving from #Ruby byebug to ruby/debug - specifically navigating the stack. Say I've s[tep into] a frame and now I'm done and want to finish that frame and resume where the frame returned. With byebug up would do that.

But with ruby/debug I need to fin[ish frame] and then n[ext]. While ruby/debug has up, it seems to "move" the debugger around frames, w/o actually executing anything. I suppose that makes sense, but seems different than up in byebug, no?

=> More informations about this toot | More toots from stevenharman@ruby.social

Written by Steven Harman on 2024-10-14 at 20:41

Even @st0012's great guide says up is the same in both byebug and ruby/debug, but that's not what I'm seeing. Though… now that I've said it, I'm wondering if this is a specific way that pry-byebug interacts?

i.e., maybe pry-byebug is making up behave differently than vanilla byebug?

[#]Ruby

=> More informations about this toot | More toots from stevenharman@ruby.social

Toot

Written by Henry Maddocks on 2024-10-15 at 04:59

@stevenharman @st0012 IME pry does unexpected things

=> More informations about this toot | More toots from acute_distress@ruby.social

Descendants