[NaCl SDK Docs] Remove links to developers.google.com

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 71 matching lines @@
 <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
 <a class="reference external" href="https://developer.mozilla.org/en/DOM/console.log">console.log()</a> to write
-the message to the JavaScript <a class="reference external" href="https://developers.google.com/chrome-developer-tools/docs/console">console</a> in
+the message to the JavaScript <a class="reference external" href="/devtools/docs/console-api">console</a> in
 Chrome&#8217;s Developer Tools.</p>
 </section><section id="debugging-with-printf">
 <h3 id="debugging-with-printf">Debugging with printf</h3>
 <p>Your C/C++ code can perform inline printf debugging to stdout and stderr by
 calling fprintf() directly, or by using cover functions like these:</p>
 <pre class="prettyprint">
 #include &lt;stdio.h&gt;
 void logmsg(const char* pMsg){
   fprintf(stdout,&quot;logmsg: %s\n&quot;,pMsg);
 }
@@ skipping 249 matching lines @@
 </dd>
 <dt><code>--user-data-dir=&lt;directory&gt;</code></dt>
 <dd><p class="first last">Specifies the <a class="reference external" href="http://www.chromium.org/user-experience/user-data-directory">user data directory</a> from which
 Chrome should load its state.  You can specify a different user data
 directory so that changes you make to Chrome in your debugging session do
 not affect your personal Chrome data (history, cookies, bookmarks, themes,
 and settings).</p>
 </dd>
 <dt><code>--nacl-debug-mask=&lt;nmf_url_mask1,nmf_url_mask2,...&gt;</code></dt>
 <dd><p class="first last">Specifies a set of debug mask patterns. This allows you to selectively
-choose to debug certain applications and not debug others. For example,
-if you only want to debug the NMF files for your applications at
-<code>https://example.com/app</code>, and no other NaCl applications found
-on the web, specify <code>--nacl-debug-mask=https://example.com/app/*.nmf</code>.
-This helps prevent accidentally debugging other NaCl applications if
-you like to leave the <code>--enable-nacl-debug</code> flag turned on.
-The pattern language for the mask follows <a class="reference external" href="http://developer.chrome.com/extensions/match_patterns">chrome extension match patterns</a>.
-The pattern set can be inverted by prefixing the pattern set with
-the <code>!</code> character.</p>
+choose to debug certain applications and not debug others. For example, if
+you only want to debug the NMF files for your applications at
+<code>https://example.com/app</code>, and no other NaCl applications found on the
+web, specify <code>--nacl-debug-mask=https://example.com/app/*.nmf</code>.  This
+helps prevent accidentally debugging other NaCl applications if you like
+to leave the <code>--enable-nacl-debug</code> flag turned on.  The pattern language
+for the mask follows <a class="reference external" href="/extensions/match_patterns">chrome extension match patterns</a>.  The pattern set can be inverted by
+prefixing the pattern set with the <code>!</code> character.</p>
 </dd>
 <dt><code>&lt;URL&gt;</code></dt>
 <dd><p class="first last">Specifies the URL Chrome should open when it launches. The local server
 that comes with the SDK listens on port 5103 by default, so the URL when
 you&#8217;re debugging is typically <code>localhost:5103</code> (assuming that your
 application&#8217;s page is called index.html and that you run the local server
 in the directory where that page is located).</p>
 </dd>
 </dl>
 </li>
@@ skipping 164 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}}