aboutsummaryrefslogtreecommitdiffstats
path: root/doc/rawshark.pod
diff options
context:
space:
mode:
authorJeff Morriss <jeff.morriss@ulticom.com>2010-09-02 18:02:06 +0000
committerJeff Morriss <jeff.morriss@ulticom.com>2010-09-02 18:02:06 +0000
commit7d20440ff0f5c8fc1510198eda81761b273e2a67 (patch)
treeae3163d422effdd1ba05613492f197e462c37369 /doc/rawshark.pod
parent8ffbb8ade834c899790c808e479cb471680c16b5 (diff)
Introduce 2 new environment variables: WIRESHARK_EP_VERIFY_POINTERS and
WIRESHARK_SE_VERIFY_POINTERS that control whether or not we verify if a given pointer is ep_ or se_ allocated, respectively. Turn the behavior off by default for speed reasons (the speed difference isn't huge, but...). Turn the behavior on when fuzz testing. Document these two new variables in the man pages. svn path=/trunk/; revision=34046
Diffstat (limited to 'doc/rawshark.pod')
-rw-r--r--doc/rawshark.pod16
1 files changed, 15 insertions, 1 deletions
diff --git a/doc/rawshark.pod b/doc/rawshark.pod
index 6981fc172a..1a3b9db210 100644
--- a/doc/rawshark.pod
+++ b/doc/rawshark.pod
@@ -436,10 +436,24 @@ 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.
+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.
+=item WIRESHARK_EP_VERIFY_POINTERS
+
+This environment variable, if exported, causes certain uses of pointers to be
+audited to ensure they do not point to memory that is deallocated after each
+packet has been fully dissected. This can be useful to developers writing or
+auditing code.
+
+=item WIRESHARK_SE_VERIFY_POINTERS
+
+This environment variable, if exported, causes certain uses of pointers to be
+audited to ensure they do not point to memory that is deallocated after when
+a capture file is closed. This can be useful to developers writing or
+auditing code.
+
=back
=head1 SEE ALSO