Index: native_client_sdk/doc_generated/devguide/devcycle/debugging.html |
diff --git a/native_client_sdk/doc_generated/devguide/devcycle/debugging.html b/native_client_sdk/doc_generated/devguide/devcycle/debugging.html |
index 039c0ce817f3c51d8138b5e106c68603a882b73f..7de09062884e3659717ca548155ea44ae0dcde39 100644 |
--- a/native_client_sdk/doc_generated/devguide/devcycle/debugging.html |
+++ b/native_client_sdk/doc_generated/devguide/devcycle/debugging.html |
@@ -32,11 +32,7 @@ and measure your application’s performance.</p> |
</li> |
</ul> |
</li> |
-<li><p class="first"><a class="reference internal" href="#debugging-with-other-tools" id="id15">Debugging with other tools</a></p> |
-<ul class="small-gap"> |
-<li><a class="reference internal" href="#open-source-profiling-tools" id="id16">Open source profiling tools</a></li> |
-</ul> |
-</li> |
+<li><a class="reference internal" href="#debugging-with-other-tools" id="id15">Debugging with other tools</a></li> |
</ul> |
</div><h2 id="diagnostic-information">Diagnostic information</h2> |
@@ -477,11 +473,6 @@ 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> |
-<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> |
{{/partials.standard_nacl_article}} |