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.

Please Log In to Continue

Once upon a time, I needed to profile some code.I tried Devel::Dprof. It crashed. It producedwrong answers. It was bad.I tried a few other profilers off of cpan. They allcrashed. 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?