aboutsummaryrefslogtreecommitdiffstats
path: root/doc/rawshark.pod
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2010-04-14 00:46:29 +0000
committerGuy Harris <guy@alum.mit.edu>2010-04-14 00:46:29 +0000
commit6b67ce3ce74bd6bfcc7956ab0e1d665750878ac0 (patch)
tree578c01c56f155f5c3778ab3722fa95dd0a541a8d /doc/rawshark.pod
parent6baa3f1abe6c6c919677c604ae6375a5b0b8397f (diff)
In the section on WIRESHARK_ABORT_ON_DISSECTOR_BUG, give the name of the
program the man page describes, and give a bit more detail. svn path=/trunk/; revision=32458
Diffstat (limited to 'doc/rawshark.pod')
-rw-r--r--doc/rawshark.pod13
1 files changed, 8 insertions, 5 deletions
diff --git a/doc/rawshark.pod b/doc/rawshark.pod
index dcf7e52e29..c97dcb4f1d 100644
--- a/doc/rawshark.pod
+++ b/doc/rawshark.pod
@@ -430,11 +430,14 @@ less likely.
=item WIRESHARK_ABORT_ON_DISSECTOR_BUG
-If this environment variable is set, Wireshark will call abort(3) when a
-dissector bug is encountered. abort(3) will cause the program to exit and
-will, on some OS and assuming your environment is configured correctly,
-generate a core file. This can be useful to developers attempting to
-troubleshoot a problem with a protocol dissector.
+If this environment variable is set, B<Rawshark> will call abort(3)
+when a dissector bug is encountered. abort(3) will cause the program to
+exit abnormally; if you are running B<Rawshark> in a debugger, it
+should halt in the debugger and allow inspection of the process, and, if
+you are not running it in a debugger, it will, on some OSes, assuming
+your environment is configured correctly, generate a core dump file.
+This can be useful to developers attempting to troubleshoot a problem
+with a protocol dissector.
=back