summaryrefslogtreecommitdiff
path: root/manual/memory.texi
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1998-02-11 14:49:20 +0000
committerUlrich Drepper <drepper@redhat.com>1998-02-11 14:49:20 +0000
commit241b119df706eec5dc76bf3e63878241339f456c (patch)
treebf911b69e4b8ce61efbfcd72d78fb42cda9075f2 /manual/memory.texi
parent2d4a30ce4903fcbdf419f65412050bf32c7d1e91 (diff)
downloadglibc-241b119df706eec5dc76bf3e63878241339f456c.tar.gz
Update.
1998-02-11 Andreas Jaeger <aj@arthur.rhein-neckar.de> * manual/memory.texi (Using the Memory Debugger): Fix typo. * math/libm-test.c (modf_test): Add one more test for modf.
Diffstat (limited to 'manual/memory.texi')
-rw-r--r--manual/memory.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/manual/memory.texi b/manual/memory.texi
index 421ec797f7..4e42b47add 100644
--- a/manual/memory.texi
+++ b/manual/memory.texi
@@ -898,7 +898,7 @@ behaviour of the program it is no wise idea to call @code{mtrace} in all
programs. Just imagine you debug a program using @code{mtrace} and all
other programs used in the debug sessions also trace their @code{malloc}
calls. The output file would be the same for all programs and so is
-unusable. Therefore on should call @code{mtrace} only if compiled for
+unusable. Therefore one should call @code{mtrace} only if compiled for
debugging. A program could therefore start like this:
@example