On May 21, 5:32 pm, Eric Hodel <drbr... / segment7.net> wrote:
> On May 21, 2007, at 15:11, Joel VanderWerf wrote:
>
>
>
> > Daniel Berger wrote:
> >> Hi all,
> >> Has anyone written anything that will skip all the gem related code
> >> that occurs on startup when running a profiler over a program? Is it
> >> even possible?
> >> All that extra stuff in the final output makes it harder to read and
> >> generally bugs me.
>
> > An excerpt from the README of ruby-prof:
>
> > ==================================================
> > === ruby-prof API
>
> > The second way is to use the ruby-prof API to profile
> > particular segments of code.
>
> >   require 'ruby-prof'
>
> >   # Profile the code
> >   RubyProf.start
> >   ...
> >   [code to profile]
> >   ...
> >   result = RubyProf.stop
>
> Is RubyProf still being maintained?  It has this horribly annoying
> bug where it breaks when you return after calling RubyProf.start.
> The pure-ruby profile.rb works correctly, Shugo's prof (RubyProf's
> ancestor) works correctly, and zenprofile (from ZenHacks) works
> correctly.
>
> The bug's been reported at least twice:
>
> http://rubyforge.org/tracker/index.php?
> func=detail&aid=5652&group_id=1814&atid=7060
>
> http://rubyforge.org/tracker/index.php?
> func=detail&aid=5658&group_id=1814&atid=7060

I haven't experienced that myself, and it has been less than a year
since the last release. However, I do see a bunch of bugs in the queue
that haven't been touched, so I dunno.

Shugo, Charlie - you around?

Dan