Add documentation about how to debug non-stable PNaCl pexes in Pepper 35.

Add documentation about how to debug non-stable PNaCl pexes in Pepper 35.

Document the "remote get nexe <path>" and
"remote get irt <other-path>" commands.
Also document the --nacl-debug-mask=<pattern_set> flag.

BUG=http://code.google.com/p/nativeclient/issues/detail?id=3765
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=260303

[jvoung (off chromium), 2014-03-28 22:05:42]

https://codereview.chromium.org/217683002/diff/1/native_client_sdk/src/doc/de...
File native_client_sdk/src/doc/devguide/devcycle/debugging.rst (right):

https://codereview.chromium.org/217683002/diff/1/native_client_sdk/src/doc/de...
native_client_sdk/src/doc/devguide/devcycle/debugging.rst:274: Debugging PNaCl
pexes (with older Pepper toolchains)
My though is we can leave this for a few more releases in case people haven't
migrated to a newer Pepper version (seems like some people are still using
pepper 31)...

Does that sound reasonable?

[Sam Clegg, 2014-03-28 22:18:29]

lgtm

https://codereview.chromium.org/217683002/diff/1/native_client_sdk/src/doc/de...
File native_client_sdk/src/doc/devguide/devcycle/debugging.rst (right):

https://codereview.chromium.org/217683002/diff/1/native_client_sdk/src/doc/de...
native_client_sdk/src/doc/devguide/devcycle/debugging.rst:398: This helps
accidentally debugging other PNaCl applications if you like
Use say PNaCl here rather than NaCl.  Is that intentional?

https://codereview.chromium.org/217683002/diff/1/native_client_sdk/src/doc/de...
native_client_sdk/src/doc/devguide/devcycle/debugging.rst:497: nacl-irt
"C:/Users/<username>/AppData/Local/Google/Chrome
SxS/Application/23.0.1247.1/nacl_irt_x86_64.nexe"
Is it recommended to set the remove before calling nacl-irt and nacl-manifest?

[jvoung (off chromium), 2014-03-28 22:39:33]

https://codereview.chromium.org/217683002/diff/1/native_client_sdk/src/doc/de...
File native_client_sdk/src/doc/devguide/devcycle/debugging.rst (right):

https://codereview.chromium.org/217683002/diff/1/native_client_sdk/src/doc/de...
native_client_sdk/src/doc/devguide/devcycle/debugging.rst:398: This helps
accidentally debugging other PNaCl applications if you like
On 2014/03/28 22:18:29, Sam Clegg wrote:
> Use say PNaCl here rather than NaCl.  Is that intentional?

Not intentional -- It helps with NaCl as well, so changed to NaCl to be more
general.

https://codereview.chromium.org/217683002/diff/1/native_client_sdk/src/doc/de...
native_client_sdk/src/doc/devguide/devcycle/debugging.rst:497: nacl-irt
"C:/Users/<username>/AppData/Local/Google/Chrome
SxS/Application/23.0.1247.1/nacl_irt_x86_64.nexe"
On 2014/03/28 22:18:29, Sam Clegg wrote:
> Is it recommended to set the remove before calling nacl-irt and nacl-manifest?

I moved "target remote ..." earlier in case people start using "remote get irt
...".

Otherwise, the original ordering may have been prettier if the IRT had symbol
names. Then the initial breakpoint will have the "_start" name. However, I think
recent IRTs shipped with chrome are fully stripped, so either way of loading the
IRT (from C:/.../Chrome../ or with "remote get irt") is not pretty. We'll have
to figure out a better way to get an IRT with debug info and symbols.

Still, it's useful to have the IRT even if it's stripped, to get stack unwinding
information if people compile without frame pointers.

[jvoung (off chromium), 2014-03-28 23:02:23]

The CQ bit was checked by jvoung@chromium.org

[commit-bot: I haz the power, 2014-03-28 23:03:33]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jvoung@chromium.org/217683002/20001

[commit-bot: I haz the power, 2014-03-28 23:46:11]

Change committed as 260303