Byebug continues when next command is used.

[bdhowald]

Often when stopped at a byebug debugger in my code, I will input next ('n'), but my server continues execution as though I clicked continue. I have tried with several different servers: puma, webrick, and thin, and all have this problem. However, it does not seem to be a problem when running a rails console or when I replace byebug in my server code with the new ruby 2.0 debugger.

[deivid-rodriguez]

It seems related (or the same) as #16 : errors in stack calculation. I guess this would be the opposite case, if the calculated stack is too big it will step, otherwise it will "continue".

I'm trying to find time for byebug, but this issues are not easy... I'll let you know when I make progress.

By the way, what's the new ruby 2.0 debugger?

[deivid-rodriguez]

Closing this in favor of #16. Feel free to reopen if you think the issues are different.