diff options
| author | Jeff Morriss <jeff.morriss.ws@gmail.com> | 2015-02-04 10:32:02 -0500 |
|---|---|---|
| committer | Anders Broman <a.broman58@gmail.com> | 2015-02-06 08:11:49 +0000 |
| commit | 0b0f7fa0911814cb824922b1740a94381ce4d265 (patch) | |
| tree | f5ca73777789cc78f3ec3b292fa9bf97807ebf5b /doc/tshark.pod | |
| parent | 881ff5df92a1c12a3afaeea3f422cb36f6e84b59 (diff) | |
More emem removal.
Remove emem's 8-byte-memory-alignment configure check as well as references
to all the environment variables emem used.
Change-Id: I897aec9e9c68e064454561e7a9f066b18892ec66
Reviewed-on: https://code.wireshark.org/review/6950
Petri-Dish: Alexis La Goutte <alexis.lagoutte@gmail.com>
Reviewed-by: Anders Broman <a.broman58@gmail.com>
Diffstat (limited to 'doc/tshark.pod')
| -rw-r--r-- | doc/tshark.pod | 54 |
1 files changed, 0 insertions, 54 deletions
diff --git a/doc/tshark.pod b/doc/tshark.pod index a3c7e305af..9bd161562f 100644 --- a/doc/tshark.pod +++ b/doc/tshark.pod @@ -1692,39 +1692,6 @@ On Windows, Wireshark normally stores all application data in %APPDATA% or %USERPROFILE%. You can override the default location by exporting this environment variable to specify an alternate location. -=item WIRESHARK_DEBUG_EP_NO_CHUNKS - -Normally per-packet memory is allocated in large "chunks." This behavior -doesn't work well with debugging tools such as Valgrind or ElectricFence. -Export this environment variable to force individual allocations. -Note: disabling chunks also disables canaries (see below). - -=item WIRESHARK_DEBUG_SE_NO_CHUNKS - -Normally per-file memory is allocated in large "chunks." This behavior -doesn't work well with debugging tools such as Valgrind or ElectricFence. -Export this environment variable to force individual allocations. -Note: disabling chunks also disables canaries (see below). - -=item WIRESHARK_DEBUG_EP_NO_CANARY - -Normally per-packet memory allocations are separated by "canaries" which -allow detection of memory overruns. This comes at the expense of some extra -memory usage. Exporting this environment variable disables these canaries. - -=item WIRESHARK_DEBUG_SE_USE_CANARY - -Exporting this environment variable causes per-file memory allocations to be -protected with "canaries" which allow for detection of memory overruns. -This comes at the expense of significant extra memory usage. - -=item WIRESHARK_DEBUG_SCRUB_MEMORY - -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. - =item WIRESHARK_DEBUG_WMEM_OVERRIDE Setting this environment variable forces the wmem framework to use the @@ -1783,27 +1750,6 @@ 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. -=item WIRESHARK_EP_VERIFY_POINTERS - -This environment variable, if present, 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 present, 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. - -=item WIRESHARK_ABORT_ON_OUT_OF_MEMORY - -This environment variable, if present, causes abort(3) 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 |