Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Dreaming of a Better Profiler More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

I did. But no more. (Score:1)

by jaw (3937) on 2004.05.26 23:12 (#31117) Homepage

Once upon a time, I needed to profile some code.
I tried Devel::Dprof. It crashed. It produced
wrong answers. It was bad.
I tried a few other profilers off of cpan. They all
crashed. They all produced wrong answers.
I may have cried.

I sat and I sat, and I thought and I thought.
And then I wrote Devel::Profile.
It didn't crash. It produced reasonable answers.
It was good. I may have danced. I may have sang.

Try it. You'll like it. It's on CPAN.

Reply to This
- Re:I did. But no more. (Score:2)
  
  by samtregar (2699)
  
  Yeah, I did. I was pretty surprised. So what's the secret? How does Devel::Profile use the DB hooks but not crash when other DB profilers crash? I'm 99% certain that the crashes in Devel::DProf are really crashes in the DB debugger hooks. So how do you avoid them?
  -sam
  - Re:I did. But no more. (Score:1)
    
    by jaw (3937)
    
    the only "secrets" are keeping it really
    really simple, programming like you're in a
    china shop: be careful not to touch anything
    that might fall and break.
- Re:I did. But no more. (Score:1)
  
  by slanning (5049)
  
  I hope to make it work with Bricolage, then. Thanks.
  - Re:I did. But no more. (Score:1)
    
    by slanning (5049)
    
    Works. Yay.

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.