summaryrefslogtreecommitdiffstats
path: root/native_client_sdk/src
diff options
context:
space:
mode:
Diffstat (limited to 'native_client_sdk/src')
-rw-r--r--native_client_sdk/src/doc/devguide/devcycle/debugging.rst1
-rw-r--r--native_client_sdk/src/doc/sdk/release-notes.rst10
2 files changed, 11 insertions, 0 deletions
diff --git a/native_client_sdk/src/doc/devguide/devcycle/debugging.rst b/native_client_sdk/src/doc/devguide/devcycle/debugging.rst
index 35cba5a..0e2503e 100644
--- a/native_client_sdk/src/doc/devguide/devcycle/debugging.rst
+++ b/native_client_sdk/src/doc/devguide/devcycle/debugging.rst
@@ -231,6 +231,7 @@ that matches the SDK version. Developers who may have left the
copy of your application (which may or may not work, depending on
their version of Chrome).
+.. _debugging_pexes_via_nexes:
Debugging PNaCl pexes (with older Pepper toolchains)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/native_client_sdk/src/doc/sdk/release-notes.rst b/native_client_sdk/src/doc/sdk/release-notes.rst
index 8fbf326..e88569a 100644
--- a/native_client_sdk/src/doc/sdk/release-notes.rst
+++ b/native_client_sdk/src/doc/sdk/release-notes.rst
@@ -19,6 +19,16 @@ PNaCl
SDK can therefore generate them.
* Fix a `code generation bug on ARM`_ when dealing with 16-bit load/store and
``bswap`` which led to a NaCl validation failure.
+* PNaCl is now based on LLVM 3.6. If you are using GDB to debug PNaCl
+ :ref:`BC files with debug metadata in the browser<debugging_pnacl_pexes>`,
+ remember that debug info from SDK version ``X`` is only compatible with the
+ PNaCl translator in chrome version ``X``. The bitcode debug metadata format
+ changed from LLVM 3.5 to 3.6. If you need to debug an app built with SDK
+ version ``X`` running in Chrome version ``Y`` (with ``X != Y``), it is still
+ possible to do so. Simply translate the pexe to a nexe using the
+ :ref:`offline pnacl-translate tool from SDK version X
+ <debugging_pexes_via_nexes>` instead of using the translator in the
+ browser (version ``Y``).
.. _`code generation bug on ARM`: https://code.google.com/p/chromium/issues/detail?id=460432