Project

General

Profile

Bug #10148

[TracePoint API] Extra block events generated

Added by David Rodríguez almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
ruby -v:
ruby 2.2.0dev (2014-08-19 trunk 47220) [i686-linux]
[ruby-core:64451]

Description

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!!

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

History

#1 [ruby-core:64589] Updated by Tomoyuki Chikanaga almost 2 years ago

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

#2 [ruby-core:66519] Updated by Koichi Sasada over 1 year ago

Could you check it again?

#3 [ruby-core:66553] Updated by David Rodríguez over 1 year ago

I will, soon!

#4 [ruby-core:66579] Updated by David Rodríguez over 1 year 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.

#5 [ruby-core:66604] Updated by Koichi Sasada over 1 year ago

  • Status changed from Assigned to Closed

Thank you!

#6 [ruby-core:66614] Updated by David Rodríguez over 1 year ago

Thanks to you!

Also available in: Atom PDF