Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Scott Johnson's Blog:
A PHP Debugging Tip Too Useful Not to Blog
Jun 16, 2006 @ 05:54:34

In this new post Scott Johnson shares a PHP debugging tip that's "too useful not to blog".

Every so often you, in a fit of frustration, you whip out a little internal tool — perhaps a debugging hack — that all of a sudden just makes things much more clear and then you feel good and, for me, that means blogging it.

Now I'm not a fan of IDE's for php coding — but I will acknowledge freely that an IDE makes this kind of debugging much easier — so I whipped up get_caller_context, a debugging function, to support this.

The function he describes performs similar to a call to debug_print_backtrace but with a bit less output. He gives a simple example of what that output would be as well as a brief explaination as to what it means. And, of course, he also includes a link to the code.

tagged: debugging tip useful get_caller_context debug_print_backtrace debugging tip useful get_caller_context debug_print_backtrace

Link:

Scott Johnson's Blog:
A PHP Debugging Tip Too Useful Not to Blog
Jun 16, 2006 @ 05:54:34

In this new post Scott Johnson shares a PHP debugging tip that's "too useful not to blog".

Every so often you, in a fit of frustration, you whip out a little internal tool — perhaps a debugging hack — that all of a sudden just makes things much more clear and then you feel good and, for me, that means blogging it.

Now I'm not a fan of IDE's for php coding — but I will acknowledge freely that an IDE makes this kind of debugging much easier — so I whipped up get_caller_context, a debugging function, to support this.

The function he describes performs similar to a call to debug_print_backtrace but with a bit less output. He gives a simple example of what that output would be as well as a brief explaination as to what it means. And, of course, he also includes a link to the code.

tagged: debugging tip useful get_caller_context debug_print_backtrace debugging tip useful get_caller_context debug_print_backtrace

Link: