PHP debug_backtrace in production code to get information about calling method?

Question

Is there a compelling reason to not use debug_backtrace for the sole purpose of determining the calling method\'s class, name, and parameter list? Not for debugging purposes

Answer 1

I'm thinking about using the debug_backtrace for debugging mysql statements. It's a hell a lot of easier to pinpoint erroneous or slow queries when you have a header like this at the start of each query inside the database logs:

/*Called from /var/www/micimacko.php at line 28*/ SELECT count(*) FROM rofibeka;

The question remains. What about performance/reliability.