Current problem reports assigned to freebsd-threads@FreeBSD.org
bugmaster at FreeBSD.org
Mon Sep 8 02:22:29 UTC 2008
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker Resp. Description
o threa/126950 threads [patch] rtld(1): rtld malloc is thread-unsafe
o kern/126128 threads [patch] pthread_condattr_getpshared is broken
o threa/122923 threads 'nice' does not prevent background process from steali
o threa/121336 threads lang/neko threading ok on UP, broken on SMP (FreeBSD 7
o threa/118715 threads kse problem
o threa/116668 threads can no longer use jdk15 with libthr on -stable SMP
o threa/116181 threads /dev/io-related io access permissions are not propagat
o threa/115211 threads pthread_atfork misbehaves in initial thread
o threa/110636 threads [request] gdb(1): using gdb with multi thread applicat
o threa/110306 threads apache 2.0 segmentation violation when calling gethost
o threa/103975 threads Implicit loading/unloading of libpthread.so may crash
o threa/101323 threads fork(2) in threaded programs broken.
s threa/100815 threads FBSD 5.5 broke nanosleep in libc_r
s threa/94467 threads send(), sendto() and sendmsg() are not correct in libc
s threa/84483 threads problems with devel/nspr and -lc_r on 4.x
o threa/83914 threads [libc] popen() doesn't work in static threaded program
o threa/80992 threads abort() sometimes not caught by gdb depending on threa
o threa/80435 threads panic on high loads
o threa/79887 threads [patch] freopen() isn't thread-safe
o threa/79683 threads svctcp_create() fails if multiple threads call at the
s threa/76694 threads fork cause hang in dup()/close() function in child (-l
s threa/76690 threads fork hang in child for -lc_r
o threa/75374 threads pthread_kill() ignores SA_SIGINFO flag
o threa/75273 threads FBSD 5.3 libpthread (KSE) bug
o threa/72953 threads fork() unblocks blocked signals w/o PTHREAD_SCOPE_SYST
o threa/70975 threads [sysvipc] unexpected and unreliable behaviour when usi
s threa/69020 threads pthreads library leaks _gc_mutex
s threa/49087 threads Signals lost in programs linked with libc_r
s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under
s threa/40671 threads pthread_cancel doesn't remove thread from condition qu
s threa/39922 threads [threads] [patch] Threaded applications executed with
s threa/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwrite() need wra
s threa/34536 threads accept() blocks other threads
s bin/32295 threads pthread(3) dont dequeue signals
s threa/30464 threads pthread mutex attributes -- pshared
s threa/24632 threads libc_r delicate deviation from libc in handling SIGCHL
s threa/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket o
37 problems total.
Bugs can be in one of several states:
o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the
originator or the community - possibly confirmation of
the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or
confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on
a repocopy operation within the CVS repository which
is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information
or resources. This is a prime candidate
for somebody who is looking for a project to do.
If the problem cannot be solved at all,
it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated,
documented, and tested -- or when fixing the problem is abandoned.
More information about the freebsd-threads