postpostmodern

pinecone-dot-website

<p>dbug() dlog() ddbug()</p>
<h3>dbug Basics</h3>
<h4>Debugging</h4>
<p>Call with up to three arguments:<br />
    <?php<br />
        // output a variable<br />
        dbug( $var );</p>
<pre><code>    // output a variable with a title           
    dbug( $debug, 'Testing' );

    // output a variable with a title and information from the last 6 steps from debug_backtrace
    dbug( $somevalue, 'Trying to figure some shit out', 6 );
}
</code></pre>
<p>or use <code>ddbug</code> to dbug and die.</p>
<h4>Error Logging</h4>
<p>Call with up to three arguments:<br />
    <?php<br />
        // log a variable<br />
        dlog( $val );</p>
<pre><code>    // log a variable with a title
    dlog( $buggy, 'what is $buggy' );

    // log a variable with a title into the file 'bug_trap' 
    dlog( $somevalue, 'im desperate', 'bug_trap' );
}
</code></pre>
<h4>Production / Development Environments</h4>
<p>you should have them</p>


dbug

Simple error debugging and logging functions.

Fumiki Takahashi

TAROSKY INC.

Kunoichi INC

<p>Have you ever seen an error log like the one below?</p>
<blockquote>
<p>PHP Fatal error: Allowed memory size of xxxxxx bytes exhausted (tried to allocate xxx bytes) in /var/www/wordpress/wp-includes/wp-db.php on line 2007</p>
</blockquote>
<p>This means that <a href="https://www.php.net/manual/en/ini.core.php#ini.memory-limit" rel="nofollow ugc">PHP memory limit</a> is exhausted while retrieving data from a database. In any case, this happens when your site has big data and makes insane loops inside.</p>
<p>But we want to know that <strong>which plugin tried to retrieve data?</strong></p>
<p>Hagakure adds extra information to error.log file when <code>wp-db.php</code> causes memory limit error:</p>
<pre>[08-May-2019 10:28:37 UTC] wpdb Error Backtrace:
#1      Kunoichi\Hagakure\DbLogger->filter_query()      /app/public/wp-includes/class-wp-hook.php       Line 286
#2      WP_Hook->apply_filters()        /app/public/wp-includes/plugin.php      Line 208
#3      apply_filters   /app/public/wp-includes/wp-db.php       Line 1871
#4      wpdb->query()   /app/public/wp-includes/wp-db.php       Line 2579
#5      wpdb->get_results()     /app/public/wp-includes/class-wp-query.php      Line 2979
#6      WP_Query->get_posts()   /app/public/wp-includes/class-wp-query.php      Line 3387
#7      WP_Query->query()       /app/public/wp-includes/post.php        Line 1961
#8      get_posts       /app/public/wp-content/plugins/hagakure/hagakure.php    Line 34
#9      {closure}       /app/public/wp-includes/class-wp-hook.php       Line 286
#10     WP_Hook->apply_filters()        /app/public/wp-includes/class-wp-hook.php       Line 310
#11     WP_Hook->do_action()    /app/public/wp-includes/plugin.php      Line 465
#12     do_action       /app/public/wp-includes/template-loader.php     Line 13
#13     require_once    /app/public/wp-blog-header.php  Line 19
#14     require /app/public/index.php   Line 17
#15     URI: /?p=1</pre>
<p>This log will always follow the memory limit Fatal Error by <code>wp-db.php</code>. Now you can find <code>#8</code> calls <code>get_posts</code> repeatedly.</p>
<p>We recommend watching logs with notification services like <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html" rel="nofollow ugc">CloudWatch Logs</a>.<br />
This error occurs in the productional environment, and you may not have a chance to see it occurs.<br />
We use Hagakure with our <a href="https://hosting.kunoichiwp.com/" rel="nofollow ugc">hosting service</a>, please look forward to seeing <a href="https://kunoichiwp.com/blog" rel="nofollow ugc">our blog published</a> and describing the integration!</p>
<p>This plugin also adds debug backtrace to error logs. To modify the error level to a detailed backtrace, define the constant in <code>wp-config.php</code> or somewhere else:</p>
<pre>define( 'HAGAKURE_ERROR_LEVEL', E_NOTICE | E_USER_WARNING | E_WARNING | E_USER_ERROR );</pre>
<p>Besides that, if <code>SAVEQUERIES</code> is set <code>true</code>, the slow query log will be logged with PHP debug backtrace. This helps you to debug.</p>
<h3>Acknowledgements</h3>
<p>The base text for dummy content is “Three Ghost Story” by Charles Dickens. The text file is modified the one of <a href="https://www.gutenberg.org/ebooks/1289" rel="nofollow ugc">Project Gutenberg</a>.</p>


Hagakure – Yet Another Error Reporter

This plugin makes it easy to find the root cause of PHP Fatal error: Allowed memory size of xxxxxx bytes exhausted error. AWESOME.


Great

Looks good

A WordPress plugin to clarify meaningless errors like "Allowed memory size of xxxxxxxx bytes exhausted".

dbug vs Hagakure – Yet Another Error Reporter