List of known bugs (certainly very incomplete)
----------------------------------------------
-Time-stamp: <02/09/30 13:49:48 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.org: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. Before reporting
-a bug please check the FAQ since it discusses also a lot of problematic
-situations.
+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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ **] 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 RPC code is not 64 bit clean. This is getting slowly fixed
but expect incompatible changes on 64 bit platforms like Alpha.
-[ **] If a DSO is using implicitly libpthread and the application itself
- does not there is a name lookup problem. E.g., the function fork()
- will be found in the libc.so instead of libpthread since the thread
- library is behind the libc. To correct this problem it must *not*
- be relied on the currently still enabled handling of weak symbols
- in the dynamic linker. Instead explicit tests for the availability
- of the libpthread version are needed. [PR libc/2325]
-
[ *] The precision of the `sinhl' and/or `asinhl' function do not seem
to be the best.