Bug #10148: [TracePoint API] Extra block events generated

• Status: Closed
• Assignee: ko1 (Koichi Sasada)
• Target version: 2.2.0
• ruby -v: ruby 2.2.0dev (2014-08-19 trunk 47220) [i686-linux]
• Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN

[deivid (David Rodríguez)]

In the same example from #9759 (which I attach here to provide a failing test), there is a couple of b_call/b_return events that I don't think should get generated. I pointed that out in this comment: https://bugs.ruby-lang.org/issues/9759#note-1

This couple of events are not present in ruby's backtrace and sometimes they have a nil method_id which was making byebug crash as I was not expecting that. I haven't been able to reproduce this nil method_id thing in a toy program but in any case I think the proper solution to this would be not to generate these events.

Thanks!!

[nagachika (Tomoyuki Chikanaga)]

• Category set to core
• Status changed from Open to Assigned
• Assignee set to ko1 (Koichi Sasada)

[ko1 (Koichi Sasada)]

Could you check it again?

[deivid (David Rodríguez)]

I will, soon!

[deivid (David Rodríguez)]

I just revisited this and I think it was a misunderstanding on my side. The current behaviour is just fine. The issue can be closed.

[ko1 (Koichi Sasada)]

• Status changed from Assigned to Closed

Thank you!

[deivid (David Rodríguez)]

Thanks to you!