Geir Magnusson Jr. wrote:
Artem Aliev wrote:
Gier,
The DRLVM uses SIGUSR2 in thread suspend algorithm.
hysock_select() returns EINTR error when the signal appears, and
Socket.accept() throws exception.
The New ThreadManager use thread_suspend() more extensively ( in lock
reservation algorithm). So the problem appears more frequently.
Excellent - I knew there had to be an explanation as to why the same
symptom appears so much faster...
Following patch to hysock.c fixes the problem in hysock.
Probably classlib experts could provide better way to fix this problem.
This seems wrong - that we're going to make it everyone else's problem
because we're using SIGUSR2. Is there a way to setup a handler such
that select() (and other things scattered about, including user native
code) don't have to worry about this?
Well, a quick read of Stevens says "apparently not" :) It's been about
8 years since I did this kind of thing in anger.
I suspect Dalibor has a suggestion here because of Kaffe :)
geir
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
