aboutsummaryrefslogtreecommitdiff
path: root/BUGS
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2004-12-22 20:10:10 +0000
committerUlrich Drepper <drepper@redhat.com>2004-12-22 20:10:10 +0000
commita334319f6530564d22e775935d9c91663623a1b4 (patch)
treeb5877475619e4c938e98757d518bb1e9cbead751 /BUGS
parent0ecb606cb6cf65de1d9fc8a919bceb4be476c602 (diff)
downloadglibc-a334319f6530564d22e775935d9c91663623a1b4.tar
glibc-a334319f6530564d22e775935d9c91663623a1b4.tar.gz
glibc-a334319f6530564d22e775935d9c91663623a1b4.tar.bz2
glibc-a334319f6530564d22e775935d9c91663623a1b4.zip
(CFLAGS-tst-align.c): Add -mpreferred-stack-boundary=4.
Diffstat (limited to 'BUGS')
-rw-r--r--BUGS14
1 files changed, 12 insertions, 2 deletions
diff --git a/BUGS b/BUGS
index d0d5056ffc..9ff95155ef 100644
--- a/BUGS
+++ b/BUGS
@@ -1,7 +1,7 @@
List of known bugs (certainly very incomplete)
----------------------------------------------
-Time-stamp: <2005-09-23 13:25:42 drepper>
+Time-stamp: <02/09/30 13:49:48 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,7 +10,7 @@ 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://sourceware.org/bugzilla/
+ 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
@@ -27,9 +27,19 @@ 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 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.