Ruby Issue Tracking System

04/19/2014

01:11 PM ruby-trunk Bug #9759: [TracePoint API] return event missing when raising exception

Also, I'm not sure whether those `[:b_call, :create]` and `[:b_return, :create]` events should be emitted at all. The...

12:08 PM ruby-trunk Bug #9759 (Open): [TracePoint API] return event missing when raising exception

I think I found another bug in the TracePoint API, which seems related to #9321. In this case, the failing event is a...

04/17/2014

07:54 AM ruby-trunk Bug #9321: rb_mod_const_missing does not generate a c-return event

Thanks Koichi, appreciated. :)

04/01/2014

11:45 AM ruby-trunk Bug #9321: rb_mod_const_missing does not generate a c-return event

As far as I'm concerned, this changes an (incorrect) behaviour and it should be backported. In byebug's case, having ...

03/31/2014

02:10 PM ruby-trunk Bug #9321: rb_mod_const_missing does not generate a c-return event

no no I was missing something.... :( I thought this bug fix was included in 2.1 but it's not. Last master works fine....

03/30/2014

04:32 PM ruby-trunk Bug #9321: rb_mod_const_missing does not generate a c-return event

Hi @koichi, I'm still running into this issue... :( I really don't know what's going on, because the tests pass in ru...

01/07/2014

08:10 PM ruby-trunk Bug #9321: rb_mod_const_missing does not generate a c-return event

It sounds good to me. Any behavior with a balanced count of `call` and `return` events work.
Big thanks @ko1.

05:04 PM ruby-trunk Bug #9321: rb_mod_const_missing does not generate a c-return event

@drkaes If this only happens in certain c-methods it certainly looks like a bug. Thanks for working on this.
Thank...

01/06/2014

03:56 AM ruby-trunk Bug #9321: rb_mod_const_missing does not generate a c-return event

In byebug, the problem is I don't manually mantain the call stack, but only keep track of the stack size through the ...

01/04/2014

02:10 AM ruby-trunk Bug #9321: rb_mod_const_missing does not generate a c-return event

But when raising an exception from ruby, return events are emitted... Shouldn't this 2 cases be consistent?