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.
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?
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.
I did. But no more. (Score:1)
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.
Re:I did. But no more. (Score:2)
-sam
Re:I did. But no more. (Score:1)
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)
Re:I did. But no more. (Score:1)