diff options
| -rw-r--r-- | doc/rawshark.pod | 13 | ||||
| -rw-r--r-- | doc/tshark.pod | 13 | ||||
| -rw-r--r-- | doc/wireshark.pod.template | 13 |
3 files changed, 24 insertions, 15 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 diff --git a/doc/tshark.pod b/doc/tshark.pod index dbab99c300..df326a14c6 100644 --- a/doc/tshark.pod +++ b/doc/tshark.pod @@ -1082,11 +1082,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<TShark> will call abort(3) +when a dissector bug is encountered. abort(3) will cause the program to +exit abnormally; if you are running B<TShark> 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 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 |