> I understand that your program is huge and very difficult to trim down
> to a one page program that still exhibits the behaviour you are
> encountering, but if you could do that, it would be much more possible
> to find out the cause.
i will try that....
> This is impossible. If a thread T calls a method M, M is run in T, no
> matter which object or class M belongs to. Unless M is or leads to a
> notify(), there is no way M wakes up any other thread. Even when M
> leads to a notify(), the waken thread will just resume what it has
> been doing; M is still run by T, not the waken thread.
>
> Thus, if by "dummy method" you really mean it, it cannot wake up any
> thread, period.
then strange enough that it works :D
computation is made by methods (which may contain yields) called through a
select in the run-method of each thread, after computation the thread is
blocked by a self-build semaphor. Each thread has a wake method, which sets
the desired computation and send a notify to unblock the semaphor. The dummy
method contains only a return, nothing more.
> What I think really happened is that your timer thread T is doing all
> the work, giving you the impression that the program is making
> progress, while all other threads are still blocked and not waken.
but that's not what the debugger reports.... when using the timer, and hitting
threads, at any time is see different threads alive, without the timer, all
threads are asleep after a while.....
so this seems very strange....
--
ciao bboett
==============================================================
[EMAIL PROTECTED]
http://inforezo.u-strasbg.fr/~bboett http://erm1.u-strasbg.fr/~bboett
===============================================================
the total amount of intelligence on earth is constant.
human population is growing....
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
