kunalb

<ul>
<li>Call <code>kb_debug</code> with any arguments that you want to log and they will be pretty printed at the end of the document.</li>
<li>To log and show a list of all warnings, errors and notices generated by your plugin, add  <code>?KB_Debug_Errors</code> to your URL. </li>
<li>To see a list of all hooks in the order they fire as well as what arguments they are called with and what functions run on them (again, in which order),<br />
add a <code>?KB_Debug_Hooks</code> to the URL.</li>
</ul>
<p>To see both just add ?KB_Debug_Errors&KB_Debug_Hooks. (Essentially $_GET[var] must be set to enable that feature).</p>
<h3>Features</h3>
<ul>
<li>Logs and displays all warnings, errors, etc. alongwith their context.</li>
<li>Logs and displays all hooks alongwith the argument(s) each hook is called with and the functions that run on that particular hook (in order).</li>
</ul>


kb_debug.php

Reiji Sato

<p>Manage WordPress log files independently of WP_DEBUG mode.<br />
You can specify the output directory and file name, download log files, and delete them as needed.</p>
<p>By specifying a date format in the file name, you can split logs daily or monthly.</p>


WP Output Log File

Manage log files with custom directory and filename. Download and delete logs regardless of WP_DEBUG.

kb_debug.php vs WP Output Log File