aboutsummaryrefslogtreecommitdiffstats
path: root/doc/README.malloc
diff options
context:
space:
mode:
authorGerald Combs <gerald@wireshark.org>2006-05-31 19:12:15 +0000
committerGerald Combs <gerald@wireshark.org>2006-05-31 19:12:15 +0000
commiteb71f7fb96f883b748536eecde9f6f49eedbcfee (patch)
treee686fde4e5609ee0ed12778fccbded159b386785 /doc/README.malloc
parent2fd928645b5aa69feb967d00f8604b98ed0dc237 (diff)
Rename the main executable to "wireshark", along with more conversions:
ethereal.com -> wireshark.org mailing lists and addresses ETHEREAL -> WIRESHARK Man pages Automake/Autoconf names svn path=/trunk/; revision=18271
Diffstat (limited to 'doc/README.malloc')
-rw-r--r--doc/README.malloc4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/README.malloc b/doc/README.malloc
index 69619bf8d4..7e9ba9c786 100644
--- a/doc/README.malloc
+++ b/doc/README.malloc
@@ -3,7 +3,7 @@ $Id$
1. Introduction
In order to make memory management easier and to reduce the probability of
-memory leaks ethereal provides its own memory management API. This API is
+memory leaks wireshark provides its own memory management API. This API is
implemented inside epan/emem.c and provides memory allocation functions
where the allocated memory is automatically freed at certain points.
@@ -32,7 +32,7 @@ where the data is to still be available in some later packet.
The seasonal functions allocate memory that will stay around a lot longer
but will be automatically freed once the current capture is closed and
-Ethereal opens a new capture (either by reading a new capture file or by
+Wireshark opens a new capture (either by reading a new capture file or by
starting a new capture on some interface). These functions are useful for
allocations with longer scope for example if you need some buffers or data to
keep state between packets.