AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-12-22 10:50:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update.

Browse Source 
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.
This commit is contained in:
Ulrich Drepper 1998-02-11 14:49:20 +00:00
parent 2d4a30ce49
commit 241b119df7
3 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -1,3 +1,9 @@
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.
1998-02-11 14:39 Ulrich Drepper <drepper@happy.cygnus.com>
* sysdeps/unix/sysv/linux/i386/sigaction.c (__libc_missing_rt_sigs):

2
manual/memory.texi
View File

@ -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

5
math/libm-test.c
View File

@ -1714,6 +1714,11 @@ modf_test (void)
result = FUNC(modf) (21, &intpart);
check ("modf (21, &x) returns 0", result, 0);
check ("modf (21, &x) sets x to 21", intpart, 21);
result = FUNC(modf) (89.6, &intpart);
check_eps ("modf (89.6, &x) returns 0.6", result, 0.6,
CHOOSE(6e-15L, 6e-15, 2e-6));
check ("modf (89.6, &x) sets x to 89", intpart, 89);
}