From 241b119df706eec5dc76bf3e63878241339f456c Mon Sep 17 00:00:00 2001 From: Ulrich Drepper Date: Wed, 11 Feb 1998 14:49:20 +0000 Subject: Update. 1998-02-11 Andreas Jaeger * manual/memory.texi (Using the Memory Debugger): Fix typo. * math/libm-test.c (modf_test): Add one more test for modf. --- manual/memory.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'manual/memory.texi') diff --git a/manual/memory.texi b/manual/memory.texi index 421ec79..4e42b47 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 -- cgit v1.1