List of known bugs (certainly very incomplete) ---------------------------------------------- Time-stamp: <1998-03-14T09:23:56-0800 drepper> This following list contains those bugs which I'm aware of. Please make sure that bugs you report are not listed here. If you can fix one of these bugs/limitations I'll certainly be glad to receive a patch. Another source of information about bugs is the problem data base of the GNU project. There is an easy to use WWW interface available at http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl I would appreciate it very much if you could verify the problem was not reported before by looking through the database. To make the information in this database as useful as possible please report bugs always using the `glibcbug' shell script which gets installed with GNU libc. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Severity: [ *] to [***] [ **] There are problems with signal handling when using LinuxThreads. [ *] The precision of the `sinhl' and/or `asinhl' function do not seem to be the best. [ *] On Linux, there should be a way to prevent defining the symbol NGROUPS_MAX in the header file. In glibc it is defined in which must not make the other symbols in available. [PR libc/140] [ *] When assembling a locale definition, that uses the "copy" directive, with localedef, not only the copied category is checked for errors, but the whole file containing the same category. [PR libc/207 and PR libc/454] [ *] The localedef program should not generate errors if for categories which are not used for the output there are characters referenced which are not defined in the charmap. [PR libc/229] [ *] _IO_getline can loop forever, at least with C++ [PR libc/332] The problem is fixed for glibc 2.1. [ *] The rcmd() functions (more concrete: the handling of .rhosts) does not support netgroups and wildcards (+). [ **] When popen() was called with an illegal command the function still returns with a value not equal to NULL. [ *] setlocale() leaks memory. This becomes only a problem if a program calls this function very often which normally is not the case. The problem is fixed for glibc 2.1. [ *] Using the NSS modules from statically linked programs sometimes fails (for very large entries). The problem is fixed in glibc 2.1. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ulrich Drepper drepper@cygnus.com