From: "drkaes (Stefan Kaes)" Date: 2014-01-07T22:14:40+09:00 Subject: [ruby-core:59628] [ruby-trunk - Bug #9321] rb_mod_const_missing does not generate a c-return event Issue #9321 has been updated by drkaes (Stefan Kaes). Compiling with clang produces warnings: in file included from ./include/ruby/ruby.h:1694: ./include/ruby/intern.h:955:40: warning: unknown attribute 'warning' ignored [-Wattributes] void rb_frame_pop(void) __attribute__((warning("rb_frame_pop is obsolete. It will be deleted after Ruby 2.2.0.")));; You probably need to change the method signature to: DEPRECATED(void rb_frame_pop(void)); ---------------------------------------- Bug #9321: rb_mod_const_missing does not generate a c-return event https://bugs.ruby-lang.org/issues/9321#change-44157 Author: drkaes (Stefan Kaes) Status: Open Priority: Normal Assignee: Category: core Target version: ruby -v: ruby 2.1.0p1 (2013-12-26 revision 44431) [x86_64-darwin12.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN We have had an issue reported for ruby-prof where execution times were attributed incorrectly in the call graph. It turned out that the problem is caused by a missing c-return event for Module#const_missing. ruby-prof simulates the ruby call stack by subscribing to line, call, c-call, return and c-return events. Obviously, the missing return throws ruby-prof off the track. -- http://bugs.ruby-lang.org/