[NaClSDK] Docs: Fix another manifest "typo" w/ portable dict.

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 215 matching lines @@
 <p>Also, 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, otherwise GDB not might be able to print variables&#8217; values when
 debugging (this is more of a problem with the PNaCl/LLVM toolchain than
 with GCC).</p>
 <p>Once you have built a non-stable debug copy of the pexe, list the URL of
 that copy in your application&#8217;s manifest file:</p>
 <pre class="prettyprint">
 {
   &quot;program&quot;: {
-    &quot;pnacl-translate&quot;: {
-      &quot;url&quot;: &quot;release_version.pexe&quot;,
-      &quot;optlevel&quot;: 2
-    },
-    &quot;pnacl-debug&quot;: {
-      &quot;url&quot;: &quot;debug_version.bc&quot;,
-      &quot;optlevel&quot;: 0
+    &quot;portable&quot;: {
+      &quot;pnacl-translate&quot;: {
+        &quot;url&quot;: &quot;release_version.pexe&quot;,
+        &quot;optlevel&quot;: 2
+      },
+      &quot;pnacl-debug&quot;: {
+        &quot;url&quot;: &quot;debug_version.bc&quot;,
+        &quot;optlevel&quot;: 0
+      }
     }
   }
 }
 </pre>
 <p>Copy the <code>debug_version.bc</code> and <code>nmf</code> files to the location that
 your local web server serves files from.</p>
 <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
@@ skipping 291 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}}