[NaCl SDK] docs: Remove references to obsolete debugging env vars.

native_client_sdk/doc_generated/devguide/devcycle/debugging.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="debugging">
 <span id="devcycle-debugging"></span><h1 id="debugging"><span id="devcycle-debugging"></span>Debugging</h1>
 <p>This document describes tools and techniques you can use to debug, monitor,
 and measure your application&#8217;s performance.</p>
 <div class="contents local" id="table-of-contents" style="display: none">
 <p class="topic-title first">Table Of Contents</p>
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#diagnostic-information" id="id2">Diagnostic information</a></p>
@@ skipping 56 matching lines @@
 memory footprint. You can also see the rendering rate displayed as frames per
 second (FPS). Note that the computation of render frames can be performed in
 any process, but the rendering itself is always done in the top level
 application process, so look for the rendering rate there.</p>
 </section><section id="controlling-the-level-of-native-client-error-and-warning-messages">
 <h3 id="controlling-the-level-of-native-client-error-and-warning-messages">Controlling the level of Native Client error and warning messages</h3>
 <p>Native Client prints warning and error messages to stdout and stderr. You can
 increase the amount of Native Client&#8217;s diagnostic output by setting the
 following <a class="reference external" href="http://en.wikipedia.org/wiki/Environment_variable">environment variables</a>:</p>
 <ul class="small-gap">
-<li>NACL_DEBUG_ENABLE=1</li>
-<li>PPAPI_BROWSER_DEBUG=1</li>
 <li>NACL_PLUGIN_DEBUG=1</li>
-<li>NACL_PPAPI_PROXY_DEBUG=1</li>
 <li>NACL_SRPC_DEBUG=[1-255] (use a higher number for more verbose debug output)</li>
 <li>NACLVERBOSITY=[1-255]</li>
 </ul>
 </section></section><section id="basic-debugging">
 <h2 id="basic-debugging">Basic debugging</h2>
 <section id="writing-messages-to-the-javascript-console">
 <h3 id="writing-messages-to-the-javascript-console">Writing messages to the JavaScript console</h3>
 <p>You can send messages from your C/C++ code to JavaScript using the PostMessage
 call in the <a class="reference internal" href="/native-client/devguide/coding/message-system.html"><em>Pepper messaging system</em></a>. When the
 JavaScript code receives a message, its message event handler can call
@@ skipping 456 matching lines @@
 build a module into a .DLL.</p>
 <section id="open-source-profiling-tools">
 <h3 id="open-source-profiling-tools">Open source profiling tools</h3>
 <p>For the brave-hearted there are open source tools at <a class="reference external" href="http://www.chromium.org/nativeclient">Chromium.org</a> that describe how to do profiling on
 <a class="reference external" href="https://sites.google.com/a/chromium.org/dev/nativeclient/how-tos/profiling-nacl-apps-on-64-bit-windows">64-bit Windows</a>
 and <a class="reference external" href="http://www.chromium.org/nativeclient/how-tos/limited-profiling-with-oprofile-on-x86-64">Linux</a>
 machines.</p>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}