Bug #10148

[TracePoint API] Extra block events generated

Added by deivid (David Rodríguez) almost 6 years ago. Updated over 5 years ago.

Target version:
ruby -v:
ruby 2.2.0dev (2014-08-19 trunk 47220) [i686-linux]


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:

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.



test_extra_b_call_and_b_return_events.rb (1.37 KB) test_extra_b_call_and_b_return_events.rb deivid (David Rodríguez), 08/19/2014 09:27 AM

Updated by nagachika (Tomoyuki Chikanaga) almost 6 years ago

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

Updated by ko1 (Koichi Sasada) over 5 years ago

Could you check it again?

Updated by deivid (David Rodríguez) over 5 years ago

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.

Updated by ko1 (Koichi Sasada) over 5 years ago

  • Status changed from Assigned to Closed

Thank you!

Also available in: Atom PDF