libkse / libthr bugs?

[Daniel Eischen]

On Thu, 26 Jun 2003, Alex Boisvert wrote:
> Hi,
> 
> I written a small test case (see source below), which I've run against 
> both libkse and libthr.  I'm using -CURRENT as of last Tuesday and 
> running on a Dual Athlon MP 1.2 GHz (Tyan Thunder K7 motherboard).
> 
> With libkse, the program runs most of the time (say, about 9 times out 
> of 10) but sometimes hang and, interestingly, prints an "F" character to 
> the console -- but that "F" character is never printed by the 
> application itself! (see source)
> 
> Here are two examples of when it hangs:
> 
> bipolar:boisvert:~/prog/pthread:48 gcc -g -lkse -o foo2 foo2.c
> bipolar:boisvert:~/prog/pthread:49 ./foo2 1000
> Using 1000 threads (parameter)
> bar 0
> bar 1
> bar 2
> Fbar 3
> ^C
> bipolar:boisvert:~/prog/pthread:50
> 
> (Notice the "F" on  the last line, before I had to use CTRL-C to 
> terminate the application).
> 
> Also, sometimes I get:
> 
> bipolar:boisvert:~/prog/pthread:65 ./foo2 1000
> Using 1000 threads (parameter)
> F
> ^C
> bipolar:boisvert:~/prog/pthread:66

I don't really see anything wrong with your test program.  There
would seem to be a bug in libkse or perhaps even in libc (stdio
not being thread-safe or something).

We've got some changes in the works.  I'll check them out
with your test program.  Thanks!

-- 
Dan Eischen