Add NaCl SDK release note about LLVM 3.6 and debug metadata changes.

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 177 matching lines @@
 <p>When you run Chrome with <code>--enable-nacl-debug</code>, Chrome will translate
 and run the <code>debug_version.bc</code> instead of <code>release_version.pexe</code>.
 Once the debug version is loaded, you are ready to <a class="reference internal" href="#running-nacl-gdb"><em>run nacl-gdb</em></a></p>
 <p>Whether you publish the NMF file containing the debug URL to the
 release web server, is up to you. One reason to avoid publishing the
 debug URL is that it is only guaranteed to work for the Chrome version
 that matches the SDK version. Developers who may have left the
 <code>--enable-nacl-debug</code> flag turned on may end up loading the debug
 copy of your application (which may or may not work, depending on
 their version of Chrome).</p>
-<h4 id="debugging-pnacl-pexes-with-older-pepper-toolchains">Debugging PNaCl pexes (with older Pepper toolchains)</h4>
+<h4 id="debugging-pnacl-pexes-with-older-pepper-toolchains"><span id="debugging-pexes-via-nexes"></span>Debugging PNaCl pexes (with older Pepper toolchains)</h4>
 <p>If you want to use GDB to debug a program that is compiled with the PNaCl
 toolchain, you must convert the <code>pexe</code> file to a <code>nexe</code>.  (You can skip
 this step if you are using the GCC toolchain, or if you are using
 pepper 35 or later.)</p>
 <ul class="small-gap">
 <li>Firstly, make sure you are passing the <code>-g</code> <a class="reference internal" href="/native-client/devguide/devcycle/building.html#compile-flags"><em>compile option</em></a> to <code>pnacl-clang</code> to enable generating debugging info.
 You might also want to omit <code>-O2</code> from the compile-time and link-time
 options.</li>
 <li><p class="first">Secondly, use <code>pnacl-translate</code> to convert your <code>pexe</code> to one or more</p>
 <p><code>nexe</code> files.  For example:</p>
@@ skipping 266 matching lines @@
 development tools on your system, but when you&#8217;re finished developing the
 plugin, you need to port it to Native Client (i.e., build the module with one of
 the toolchains in the NaCl SDK so that the module runs in Native Client).  For
 details on this advanced development technique, see <a class="reference external" href="http://www.chromium.org/nativeclient/how-tos/debugging-documentation/debugging-a-trusted-plugin">Debugging a Trusted Plugin</a>.
 Note that starting with the <code>pepper_22</code> bundle, the NaCl SDK for Windows
 includes pre-built libraries and library source code, making it much easier to
 build a module into a .DLL.</p>
 </section>
 
 {{/partials.standard_nacl_article}}