another gdesklets kse/libc_r problem
Jeremy Messenger
mezz7 at cox.net
Mon Nov 24 01:25:43 PST 2003
On Sun, 23 Nov 2003 16:59:25 +0100, Franz Klammer <klammer at webonaut.com>
wrote:
> at least under -current i've following threads-problem:
>
> when a sensor doing commands.getstatusoutput(cmd)
> out of a thread the first call works like expected, but
> the second call will result in a deadlock (i think).
> what i've found in the last days was that it happens while
> commands.getstatusoutput -> pipe.read()
>
> if added a print "1.... "+cmd bevore getstatusoutput and
> a print "2 ... "+cmd after. heres the output if i start
> gdesklets from a terminal-window:
>
> 1 ... /bin/date '+%a %d %b %y'|iconv -t UTF-8
> 2 ... /bin/date '+%a %d %b %y'|iconv -t UTF-8
> 1 ... /bin/date '+%a %d %b %y'|iconv -t UTF-8
>
>
> that problem only occours with libc_r but not with libkse.
>
> also with libc_r a ps fax | grep gdesklets looks like this:
> 80390 p4 S+ 0:05,58 python /usr/X11R6/bin/gdesklets
> 80431 p4 S+ 0:00,00 python /usr/X11R6/bin/gdesklets
> 80446 p4 S+ 0:00,00 python /usr/X11R6/bin/gdesklets
>
> with libkse there is only one line.
>
> i'm out of ideas now.
It might be good idea to send it to freebsd-thread. I don't know if they
read in here. :-)
BTW: I will check on your PSI shar file this week, I am kind of little
busy for a little while.
Cheers,
Mezz
> franz.
--
bsdforums.org 's moderator, mezz.
More information about the freebsd-gnome
mailing list