libkse and signalling (libthr vs ports/net/linuxigd (fwd))

[Robert Watson]

I realize this message is mostly about an interaction with libthr, but
thrown in as a freebie at the bottom, the author mentions that it works
fine with libkse except that killall doesn't work (?).


Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org      Network Associates Laboratories

---------- Forwarded message ----------
Date: Fri, 30 May 2003 15:10:37 +0800
From: leafy <leafy at leafy.idv.tw>
To: freebsd-current at freebsd.org
Subject: libthr vs ports/net/linuxigd

Using libthr for upnpd produces following backtrace when starting up

#0  0x281f5b03 in _umtx_lock () from /usr/lib/libc.so.5
(gdb) backtrace
#0  0x281f5b03 in _umtx_lock () from /usr/lib/libc.so.5
#1  0x280880e8 in _spinlock_pthread (pthread=0x4, lck=0x8054130) at umtx.h:62
#2  0x28088048 in _spinlock (lck=0xc2986ab0)
    at /usr/src/lib/libthr/thread/thr_spinlock.c:69
#3  0x2808446d in mutex_lock_common (mutex=0x280d8e0c, nonblock=0)
    at /usr/src/lib/libthr/thread/thr_mutex.c:357
#4  0x28084724 in __pthread_mutex_lock (mutex=0x280d8e0c)
    at /usr/src/lib/libthr/thread/thr_mutex.c:511
#5  0x280a927a in GetNextItemInQueue(ThreadArg*, PoolQueueItem&) ()
   from /usr/local/lib/libupnp.so
#6  0x280a938e in GetNextItemInQueue(ThreadArg*, PoolQueueItem&) ()
   from /usr/local/lib/libupnp.so
#7  0x2808214c in _thread_start ()
    at /usr/src/lib/libthr/thread/thr_create.c:220
#8  0x282497a7 in _ctx_start () from /usr/lib/libc.so.5

Curiously, libkse works fine (but you can't do 'killall upnpd' with libkse 
though)

Jiawei Ye 
-- 
"Without the userland, the kernel is useless."
               --inspired by The Tao of Programming
_______________________________________________
freebsd-current at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"