Browse Source

wording improvements from Brian Poole;

kill a .Pp before a display;
OPENBSD_3_5
jmc 20 years ago
parent
commit
532d62d8fc
1 changed files with 4 additions and 5 deletions
  1. +4
    -5
      src/lib/libc/stdlib/malloc.3

+ 4
- 5
src/lib/libc/stdlib/malloc.3 View File

@ -30,7 +30,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" $OpenBSD: malloc.3,v 1.32 2003/10/16 17:05:04 tedu Exp $
.\" $OpenBSD: malloc.3,v 1.33 2003/11/25 12:32:54 jmc Exp $
.\"
.Dd August 27, 1996
.Dt MALLOC 3
@ -141,7 +141,6 @@ object is returned.
When using
.Fn realloc
one must be careful to avoid the following idiom:
.Pp
.Bd -literal -offset indent
size += 50;
if ((p = realloc(p, size)) == NULL)
@ -349,7 +348,7 @@ internal freelist has been stomped on.
Here is a brief description of the warning messages and what they mean:
.Bl -tag -width Fl
.It Dq chunk/page is already free.
A pointer to a free chunk is attempted freed again.
There was an attempt to free a chunk that had already been freed.
.It Dq junk pointer, too high to make sense.
The pointer doesn't make sense.
It's above the area of memory that
@ -422,5 +421,5 @@ Every time the free-list is traversed, all the otherwise unused, and very
likely paged out, pages get faulted into primary memory, just to see what
lies after them in the list.
.Pp
On systems which are paging, this can make a factor five in difference on the
page-faults of a process.
On systems which are paging, this can increase the page-faults
of a process by a factor of five.

Loading…
Cancel
Save