[NaCl SDK Docs] Add release notes for Chrome 34 and 35.

native_client_sdk/src/doc/devguide/devcycle/debugging.rst

 .. _devcycle-debugging:
 
 #########
 Debugging
 #########
 
 This document describes tools and techniques you can use to debug, monitor,
 and measure your application's performance.
 
 .. contents:: Table Of Contents
@@ skipping 196 matching lines @@
 <http://www.gnu.org/software/gdb/>`_, and is located at
 ``toolchain/<platform>_x86_newlib/bin/x86_64-nacl-gdb`` (where *<platform>*
 is the platform of your development machine: ``win``, ``mac``, or
 ``linux``).
 
 Note that this same copy of GDB can be used to debug any NaCl program,
 whether built using newlib or glibc for x86-32, x86-64 or ARM.  In the SDK,
 ``i686-nacl-gdb`` is an alias for ``x86_64-nacl-gdb``, and the ``newlib``
 and ``glibc`` toolchains both contain the same version of GDB.
 
+.. _debugging_pnacl_pexes:
+
 Debugging PNaCl pexes (with Pepper 35+)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you want to use GDB to debug a program that is compiled with the PNaCl
 toolchain, you must have a copy of the pexe from **before** running
 ``pnacl-finalize``. The ``pnacl-finalize`` tool converts LLVM bitcode
 to the stable PNaCl bitcode format, but it also strips out debug
 metadata, which we need for debugging.
 
 **Note** unlike the finalized copy of the pexe, the non-finalized debug copy
@@ skipping 361 matching lines @@
 <http://www.chromium.org/nativeclient>`_ that describe how to do profiling on
 `64-bit Windows
 <https://sites.google.com/a/chromium.org/dev/nativeclient/how-tos/profiling-nacl-apps-on-64-bit-windows>`_
 and `Linux
 <http://www.chromium.org/nativeclient/how-tos/limited-profiling-with-oprofile-on-x86-64>`_
 machines.
 
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. |puzzle| image:: /images/puzzle.png