List of known bugs (certainly very incomplete)
----------------------------------------------
-Time-stamp: <1997-09-28T22:58:35+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
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.
-[ **] There are problems with signal handling when using LinuxThreads.
-
-[ **] The libm-ieee `log2' function seems to be very inaccurate.
-
-[ *] The libm-ieee `remquo' function rounds 3.0/2.0 incorrectly.
+[ **] 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 <linux/posix_types.h> 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 <linux/limits.h> header file. In glibc it
is defined in <posix1_lim.h> which must not make the other
symbols in <linux/limits.h> available.
[PR libc/140]
-[ *] 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]
+[ *] 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.
-[ *] The rcmd() functions (more concrete: the handling of .rhosts) does
- not support netgroups and wildcards (+).
+[ *] 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).
-[ *] The first alias definition in locale.alias is ignored.
- [PR libc/205]
+ 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.
-[ *] 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]
+ 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.
-[ *] configuring with CFLAGS="-pipe" configure doesn't work
- with gcc. This seems to be a bug in gcc 2.7.2.x (egcs doesn't
- have this bug).
- [PR libc/245]
+[ *] 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
projects / thirdparty / glibc.git / blobdiff