>>>>> "Scott" == Scott Murray <[EMAIL PROTECTED]> writes:
> Scott Murray wrote:
>>
>> Michael Thome wrote:
>> >
>> > >>>>> "Scott" == Scott Murray <[EMAIL PROTECTED]> writes:
>> >
>> > > Michael Thome wrote:
>> > >>
>> > >> >>>>> "Calvin" == Calvin Austin <[EMAIL PROTECTED]> writes:
>> > >>
>> > >> > Submit it as a bug and/or send us the short example, it could very well be
>> > >> > another linuxthreads bug that we will have to work around or someone has
>> > >> > already discovered.
>> > >>
>> > >> Ok - I've submitted it as a bug both to the bug parade and to
>> > >> blackdown's jitterbug.
>> > >>
>> > >> For your reading pleasure, enclosed below is the current version of my
>> > >> test case. It is pretty easy to cut it down to smaller examples,
>> > >> especially if you are just looking for the Exception cases. All that
>> > >> appears to be required is tight-loop lock contention with wait/notify
>> > >> involved running on a native-threaded VM on an SMP machine (phew!).
>> >
>> > > Actually, I don't see any problems running the "Bang" example under
>> > > either 1.2.2-RC4 or Sun's beta 1.3 on my dual PIII-450 with RedHat 6.2.
>> > > It just keeps running until I kill it.
>> >
>> > Cool. What kernel+glibc are you running with? standard RedHat 6.2?
>> > Must be my kernel...
>>
>> Just the standard 2.2.12-20 kernel from RH 6.2. I may give it a whirl on
>> a 2.4.0-test2-preX kernel at home on the weekend.
> Oops. I'm also using the stock RH 6.2 glibc-2.1.3-15 package.
Just wanted to follow up on this... The scientific method led me to
discover that the culprit was the rawhide glibc-2.1.3-16 I'd
installed - going back to the stock RH 6.2 glibc seems to be working
just fine. Next step, back to the 2.3/2.4-test kernels...
Thanks much,
-mik
--
Michael Thome ([EMAIL PROTECTED])
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
