forked from osmocom/wireshark
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:
parent
6baa3f1abe
commit
6b67ce3ce7
|
@ -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
|
||||
|
||||
|
|
|
@ -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
|
||||
|
||||
|
|
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in New Issue