Lambda's and the Stack Trace about byebug HOT 12 CLOSED

Hi again, @kevjames3! As you point out, this might be related to issue #7. I opened this bug report in ruby-core which might or might not fix that. Your bug report, unlike #7, provides a way to reproduce the error so I'm going to be able to have a deeper look in to this.

Thanks a lot, I'll let you know how it goes!

from byebug.

I can confirm this behaviour in current master. I'm going to investigate this.

from byebug.

Sweet! Thanks

from byebug.

Ok, so it looks like this is a problem with the TracePoint API, similar to #5. In this case, it is related to the return keyword inside lambda's. Notice that if you remove the return inside the lambda, everything works as expected.

from byebug.

You can follow the issue here. Hopefully we'll be as lucky as in #5... :)

from byebug.

Hah, I had a feeling. In the meantime, I will be substituting its use with
Proc instead

On Wed, Jul 10, 2013 at 9:59 AM, David Rodríguez
[email protected]:

You can follow the issue here https://bugs.ruby-lang.org/issues/8622.
Hopefully we'll be as lucky as in #5#5...
:)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-20756793
.

Kevin McIntosh
Sacramento, CA
503-896-7155

from byebug.

Hi man, quick update on this... I haven't forgot about this and #7. This is reported upstream but nothing has been done yet. And I haven't had time to look at it myself and I'm not very sure I would succeed... Last news from @ko1 (TracePoint API author and ruby-core member assigned to the bugs) were

Not high priority. I want to solve these issues before 2.1 release (and feature freeze is Sep/2013).

Salute!

from byebug.

OK, I'll check it. Thank you for your reporting.

from byebug.

Great, thanks a lot! :)

from byebug.

@ko1 has just solved this! https://bugs.ruby-lang.org/issues/8622#change-42408

So we'll have a better byebug soon!

Thanks @ko1

from byebug.

(2013/10/10 19:36), David Rodríguez wrote:

@ko1 https://github.com/ko1 has just solved this!
https://bugs.ruby-lang.org/issues/8622#change-42408

sorry for late.

Any other trouble?

// SASADA Koichi at atdot dot net

from byebug.

No worries!

There's been some other trouble with the API but I was not able to isolate the problem like in this case, so maybe it was actually the same issue. I will start using the patch from today, and check whether I can reproduce those problems without this patch or not. If I find something out, I'll let you know straight away.

Thanks again!

from byebug.