osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

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
This commit is contained in:
Guy Harris 2010-04-14 00:46:29 +00:00
parent 6baa3f1abe
commit 6b67ce3ce7
3 changed files with 24 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/rawshark.pod
View File

@ -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

13
doc/tshark.pod
View File

@ -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

13
doc/wireshark.pod.template
View File

@ -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