From 388e552579aff6b5152c67adeda182d2d40e8dfc Mon Sep 17 00:00:00 2001
From: Sam Roberts <vieuxtech@gmail.com>
Date: Mon, 26 Jun 2017 11:00:34 -0700
Subject: src: document --abort-on-uncaught-exception

Its important for post-mortem diagnostics and should be more prominently
documented.

PR-URL: https://github.com/nodejs/node/pull/13931
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Julien Gilli <jgilli@nodejs.org>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
---
 doc/node.1 | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'doc/node.1')

diff --git a/doc/node.1 b/doc/node.1
index af9069f134..ca142a2cab 100644
--- a/doc/node.1
+++ b/doc/node.1
@@ -135,6 +135,10 @@ Silence all process warnings (including deprecations).
 Enable loading native modules compiled with the ABI-stable Node.js API (N-API)
 (experimental).
 
+.TP
+.BR \-\-abort\-on\-uncaught\-exception
+Aborting instead of exiting causes a core file to be generated for analysis.
+
 .TP
 .BR \-\-trace\-warnings
 Print stack traces for process warnings (including deprecations).
-- 
cgit v1.2.3