aboutsummaryrefslogtreecommitdiffstats
path: root/doc/wireshark.pod.template
diff options
context:
space:
mode:
Diffstat (limited to 'doc/wireshark.pod.template')
-rw-r--r--doc/wireshark.pod.template13
1 files changed, 10 insertions, 3 deletions
diff --git a/doc/wireshark.pod.template b/doc/wireshark.pod.template
index 0d2424d8a3..5d5224508a 100644
--- a/doc/wireshark.pod.template
+++ b/doc/wireshark.pod.template
@@ -2724,7 +2724,7 @@ This comes at the expense of significant extra memory usage.
=item WIRESHARK_DEBUG_SCRUB_MEMORY
-If this environment variable is exported, the contents of per-packet and
+If this environment variable is set, the contents of per-packet and
per-file memory is initialized to 0xBADDCAFE when the memory is allocated
and is reset to 0xDEADBEEF when the memory is freed. This functionality is
useful mainly to developers looking for bugs in the way memory is handled.
@@ -2775,14 +2775,14 @@ with a protocol dissector.
=item WIRESHARK_EP_VERIFY_POINTERS
-This environment variable, if exported, causes certain uses of pointers to be
+This environment variable, if set, 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
+This environment variable, if set, 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.
@@ -2795,6 +2795,13 @@ that. You must also specify an autostop condition, e.g. B<-c> or B<-a
duration:...>. This means that you will not be able to see the results
of the capture after it stops; it's primarily useful for testing.
+=item WIRESHARK_ABORT_ON_OUT_OF_MEMORY
+
+This environment variable, if present, causes abort() to be called if certain
+out-of-memory conditions (which normally result in an exception and an
+explanatory error message)) are experienced. This can be useful to developers
+debugging out-of-memory conditions.
+
=back
=head1 SEE ALSO