Process>suspend and resume are still broken...
Lex Spoon
lex at cc.gatech.edu
Sat Feb 26 02:32:53 UTC 2000
Just as an aside, killing or suspending threads other than your own
is dangerous and probably shouldn't be done, anyway. Suppose,
for example, that the thread in question *holds* some critical semaphore?
By suspending the thread, you are making it easy to create a deadlock.
In order to avoid this deadlock, you often end up having to have some sort of
semaphore that signals whether a thread is suspend-able or not. But if
you have to implement such a semaphore anyway, you can also just use the
semaphore to cause the process to suspend directly.
So in short, it doesn't look like this is a bug that seriously needs
fixing.....
Lex
More information about the Squeak-dev
mailing list
|