summaryrefslogtreecommitdiffstats
path: root/native_client_sdk/src/doc/devguide/devcycle/debugging.rst
diff options
context:
space:
mode:
Diffstat (limited to 'native_client_sdk/src/doc/devguide/devcycle/debugging.rst')
-rw-r--r--native_client_sdk/src/doc/devguide/devcycle/debugging.rst5
1 files changed, 4 insertions, 1 deletions
diff --git a/native_client_sdk/src/doc/devguide/devcycle/debugging.rst b/native_client_sdk/src/doc/devguide/devcycle/debugging.rst
index cd8d8b8..6a28ddb 100644
--- a/native_client_sdk/src/doc/devguide/devcycle/debugging.rst
+++ b/native_client_sdk/src/doc/devguide/devcycle/debugging.rst
@@ -222,7 +222,10 @@ 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.
+metadata, which we need for debugging. In this section we'll give the
+LLVM bitcode file a ``.bc`` file extension, and the PNaCl bitcode file
+a ``.pexe`` file extension. The actual extension should not matter, but
+it helps distinguish between the two types of files.
**Note** unlike the finalized copy of the pexe, the non-finalized debug copy
is not considered stable. This means that a debug copy of the PNaCl