>>>>> Sean Kellner writes:
Sean> Darren Steven wrote:
>>
>> Sean Kellner wrote:
>>
>> > The status report lists that the current holdup is in a threading
>> > issue. So is there any way to create a new piece of source that would
>> > display the problem without any restrictions from Sun? This would allow
>> > quite a few kernel hackers to go over it and at least see if the bug is
>> > in linuxthreads or in the code, and probably fix it. There are a few of
>> > us here who would love to help out and get this thing out the door, and
>> > this seems like the only way we can.
>> >
Sean> We still don't have anything to work with though, or even
Sean> acknoledgement that someone who is dealing with the situation has seen
Sean> my request yet.
We've seen it, it's just no that easy to create a short (or medium sized)
example that shows the problem.
Juergen
--
Juergen Kreileder, Universitaet Dortmund, Lehrstuhl Informatik V
Baroper Strasse 301, D-44221 Dortmund, Germany
Phone: ++49 231/755-5806, Fax: ++49 231/755-5802
