diff options
author | Guy Harris <guy@alum.mit.edu> | 2010-04-14 00:46:29 +0000 |
---|---|---|
committer | Guy Harris <guy@alum.mit.edu> | 2010-04-14 00:46:29 +0000 |
commit | 6b67ce3ce74bd6bfcc7956ab0e1d665750878ac0 (patch) | |
tree | 578c01c56f155f5c3778ab3722fa95dd0a541a8d /doc/wireshark.pod.template | |
parent | 6baa3f1abe6c6c919677c604ae6375a5b0b8397f (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/wireshark.pod.template')
-rw-r--r-- | doc/wireshark.pod.template | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/doc/wireshark.pod.template b/doc/wireshark.pod.template index d7411a4594..422f8349e4 100644 --- a/doc/wireshark.pod.template +++ b/doc/wireshark.pod.template @@ -2649,11 +2649,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<Wireshark> will call abort(3) +when a dissector bug is encountered. abort(3) will cause the program to +exit abnormally; if you are running B<Wireshark> 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 |