Hello,
is it possible that xmms triggers a problem in FreeBSD's thread
implementation? It happens often that xmms gets stuck in
_thread_sys_poll():
(gdb) info threads
7 process 332, thread 7 0x28439d44 in _thread_kern_sched ()
from /usr/lib/libc_r.so.4
6 process 332, thread 6 0x28439d44 in _thread_kern_sched ()
from /usr/lib/libc_r.so.4
5 process 332, thread 5 0x28439d44 in _thread_kern_sched ()
from /usr/lib/libc_r.so.4
4 process 332, thread 4 0x28439d44 in _thread_kern_sched ()
from /usr/lib/libc_r.so.4
3 process 332, thread 3 0x28439d44 in _thread_kern_sched ()
from /usr/lib/libc_r.so.4
2 process 332, thread 2 0x28439d44 in _thread_kern_sched ()
from /usr/lib/libc_r.so.4
* 1 process 332, thread 1 0x2843b754 in _thread_sys_poll ()
from /usr/lib/libc_r.so.4
(gdb)
Is this a known problem?
Bj�rn Fischer
--
-----BEGIN GEEK CODE BLOCK-----
GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+
K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+
------END GEEK CODE BLOCK------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
