native_client_sdk/src/doc/devguide/coding/progress-events.rst - Issue 2875303003: Add migration to WebAssembly information to PNaCl / NaCl docs.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: native_client_sdk/src/doc/devguide/coding/progress-events.rst

Issue 2875303003: Add migration to WebAssembly information to PNaCl / NaCl docs. (Closed)

Patch Set: fix Created 3 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « native_client_sdk/src/doc/devguide/coding/native-client-modules.rst ('k') | native_client_sdk/src/doc/devguide/coding/url-loading.rst » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 .. _devcycle-progress-events:	1 .. _devcycle-progress-events:

2	2

	3 .. include:: /migration/deprecation.inc

	4

3 ###############	5 ###############

4 Progress Events	6 Progress Events

5 ###############	7 ###############

6	8

7 .. contents::	9 .. contents::

8 :local:	10 :local:

9 :backlinks: none	11 :backlinks: none

10 :depth: 2	12 :depth: 2

11	13

12 There are five types of events that developers can respond to in Native Client:	14 There are five types of events that developers can respond to in Native Client:

(...skipping 277 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
290 crash, the ``crash`` progress event is issued and the ``exitStatus`` attribute	292 crash, the ``crash`` progress event is issued and the ``exitStatus`` attribute

291 will contain the numeric value of the exit status:	293 will contain the numeric value of the exit status:

292	294

293 * In the case of explicit calls to ``exit(n)``, the numeric value will be	295 * In the case of explicit calls to ``exit(n)``, the numeric value will be

294 ``n`` (between 0 and 255).	296 ``n`` (between 0 and 255).

295 * In the case of crashes and calls to ``abort()``, the numeric value will	297 * In the case of crashes and calls to ``abort()``, the numeric value will

296 be non-zero, but the exact value will depend on the chosen libc and the	298 be non-zero, but the exact value will depend on the chosen libc and the

297 target architecture, and may change in the future. Applications should not	299 target architecture, and may change in the future. Applications should not

298 rely on the ``exitStatus`` value being stable in these cases, but the value	300 rely on the ``exitStatus`` value being stable in these cases, but the value

299 may nevertheless be useful for temporary debugging.	301 may nevertheless be useful for temporary debugging.

OLD	NEW