diff options
| author | Steve Vinoski <[email protected]> | 2014-10-17 17:21:37 -0400 |
|---|---|---|
| committer | Steve Vinoski <[email protected]> | 2014-10-17 17:26:51 -0400 |
| commit | 0aa4dc4f66815aa4b40e8b3b2d8b9a24c180debe (patch) | |
| tree | e91be617e3a580725028c25cf81bc35425d161e1 | |
| parent | 1aa1a4f6173e9ef59ac0b6bb054368c141000062 (diff) | |
| download | otp-0aa4dc4f66815aa4b40e8b3b2d8b9a24c180debe.tar.gz otp-0aa4dc4f66815aa4b40e8b3b2d8b9a24c180debe.tar.bz2 otp-0aa4dc4f66815aa4b40e8b3b2d8b9a24c180debe.zip | |
Clarify the use of SIGUSR1 for forcing crash dumps
The crash_dump document mentions indirectly that delivering a SIGUSR1 to a
running emulator process can force it to crash dump. Clarify that text to
make it clear SIGUSR1 can be used for that purpose, and also add a similar
note about using SIGUSR1 to the erl documentation.
| -rw-r--r-- | erts/doc/src/crash_dump.xml | 5 | ||||
| -rw-r--r-- | erts/doc/src/erl.xml | 3 |
2 files changed, 5 insertions, 3 deletions
diff --git a/erts/doc/src/crash_dump.xml b/erts/doc/src/crash_dump.xml index d3de29b876..2b5fc877c3 100644 --- a/erts/doc/src/crash_dump.xml +++ b/erts/doc/src/crash_dump.xml @@ -115,8 +115,9 @@ sockets/pipes can be used simultaneously by Erlang (due to limitations in the Unix <c><![CDATA[select]]></c> call). The number of open regular files is not affected by this.</item> - <item>"Received SIGUSR1" - The SIGUSR1 signal was sent to the - Erlang machine (Unix only).</item> + <item>"Received SIGUSR1" - Sending the SIGUSR1 signal to a + Erlang machine (Unix only) forces a crash dump. This slogan reflects + that the Erlang machine crash-dumped due to receiving that signal.</item> <item>"Kernel pid terminated (<em>Who</em>) (<em>Exit-reason</em>)" - The kernel supervisor has detected a failure, usually that the <c><![CDATA[application_controller]]></c> diff --git a/erts/doc/src/erl.xml b/erts/doc/src/erl.xml index f856b9ab86..e85519185f 100644 --- a/erts/doc/src/erl.xml +++ b/erts/doc/src/erl.xml @@ -525,7 +525,8 @@ core dump and no crash dump if an internal error is detected.</p> <p>Calling <c>erlang:halt/1</c> with a string argument will still - produce a crash dump.</p> + produce a crash dump. On Unix systems, sending an emulator process + a SIGUSR1 signal will also force a crash dump.</p> </item> <tag><marker id="+e"><c><![CDATA[+e Number]]></c></marker></tag> <item> |