X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=BUGS;h=6d6ce83772ae4a9437d59e628de3c2cfc7bdd3f8;hb=0ddd15f52f742f48174597f82bee98ad9767d84a;hp=a9f2c2cc5bcf62da054af9af75f926965222f621;hpb=8f2ece695d8822e9ecc63ecd157e90bf17a6fe65;p=platform%2Fupstream%2Fglibc.git diff --git a/BUGS b/BUGS index a9f2c2c..6d6ce83 100644 --- a/BUGS +++ b/BUGS @@ -1,7 +1,7 @@ List of known bugs (certainly very incomplete) ---------------------------------------------- -Time-stamp: <1997-08-01T05:37:51+0200 drepper> +Time-stamp: <2007-10-27 18:37:51 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 @@ -10,52 +10,60 @@ 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.ai.mit.edu:8080/cgi-bin/wwwgnats.pl + http://sourceware.org/bugzilla/ -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. +I would appreciate it very much if you could verify the problem was +not reported before by looking through the database. Before reporting +a bug please check the FAQ since it discusses also a lot of +problematic situations. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Severity: [ *] to [***] +[ **] Closing shared objects in statically linked binaries most of the + times leads to crashes during the dlopen(). Hard to fix. -[ **] For GNU libc on Linux, there is still no solution for the UTMP - problem. - [Among others: PR libc/39] - -[ **] There are problems with signal handling when using LinuxThreads. - -[ **] The `cbrtl' function for ix86 does not work in the moment. - -[ **] Not really a bug, but it could lead to such: - The RPC code is ugly ugly ugly. It's more or less verbatim taken - from Sun's code and therefore mostly lacks complete prototypes and - (more important) the use of `const'. It *definitely* needs to be - cleaned. +[ **] The RPC code is not 64 bit clean. This is getting slowly fixed + but expect incompatible changes on 64 bit platforms like Alpha. [ *] The precision of the `sinhl' and/or `asinhl' function do not seem to be the best. -[ *] The syslog function should print to the console if the LOG_CONS - flag was given. - [PR libc/72] - -[ *] On Linux, the is not clean enough to satisfy - the C++ namespace rules. Declaring `struct fd_set' also makes - `fd_set' available in the global namespace which conflicts with - the definition of `fd_set' in glibc. - [PR libc/79] - [ *] 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] +[ *] The libm-ieee `gamma' function gives wrong results (at least for + -0.5). + +[ *] The libm-ieee `scalb' function gives wrong results for + non-integral second parameters. + +[ *] Several (most?) collation specifications are broken. The code which + is currently there is in most cases inherited from the originial + author (in case there is a LC_COLLATE specification in the locale + file) or is defined using the default (if iso14651_t1 is included). + + In any case we are missing information to correct the specification. + If you find the specification for your language be faulty please + send a report with instruction on what to fix. You don't have to + fix the specification yourself. + + The way it finally should look like (if the generic specification + is not correct) can be seen in the sv_SE file. Quite a few changes + on top of the generic specification can be made without duplication + of the whole LC_COLLATE description. + +[ *] Some of the functions which also handled IPv6 are currently broken. + IPv6 and IPv4 lookups occasionally happen when not needed. This + happens in getaddrinfo() and getnameinfo(). IPv4 handling of + these functions is OK though and there are patches available to fix + the IPv6 code as well. + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ulrich Drepper -drepper@cygnus.com +drepper@redhat.com