summaryrefslogtreecommitdiffstats
path: root/share/doc/papers/malloc/conclusion.ms
diff options
context:
space:
mode:
Diffstat (limited to 'share/doc/papers/malloc/conclusion.ms')
-rw-r--r--share/doc/papers/malloc/conclusion.ms8
1 files changed, 4 insertions, 4 deletions
diff --git a/share/doc/papers/malloc/conclusion.ms b/share/doc/papers/malloc/conclusion.ms
index afd64fc..05edd51 100644
--- a/share/doc/papers/malloc/conclusion.ms
+++ b/share/doc/papers/malloc/conclusion.ms
@@ -6,7 +6,7 @@
.\" this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp
.\" ----------------------------------------------------------------------------
.\"
-.\" $Id$
+.\" $Id: conclusion.ms,v 1.1 1996/04/13 08:30:11 phk Exp $
.\"
.ds RH Conclusion and experience.
.NH
@@ -23,9 +23,9 @@ Apart from that gnumalloc and this implementation are pretty
much head-on performance wise.
.PP
Several legacy programs in the BSD 4.4 Lite distribution had
-code that depended on the memory returned from malloc to
-be zeroed, in a couple of cases free(3) was called more than
-once for the same allocation and a few cases even called free(3)
+code that depended on the memory returned from malloc
+being zeroed. In a couple of cases, free(3) was called more than
+once for the same allocation, and a few cases even called free(3)
with pointers to objects in the data section or on the stack.
.PP
A couple of users have reported that using this malloc on other
OpenPOWER on IntegriCloud