Since I'm doing multiple forks of the same block, it certainly is possible
that I'm experiencing concurrent failures (stemming from the same logic leak).
I assume that why I'm getting multiple debug windows popping up.

I am attempting to write some highly threaded code (>100 processes), all able
to store into each others event queues (Heaps) - hence, the need to modify
Semaphore alluded to in my other postings!


---John



4/26/2000 9:44:16 AM, "Lex Spoon" <lex at cc.gatech.edu> wrote:

>jchludzinski at grci.com wrote:
>> Sometimes when executing some of my code, the upper left corner of the Squeak
>> main window shows a stack dump (in a white square) with the message "**System
>> error handling failed**" at the top of the square and "**Type any character to
>> continue**".
>> 
>> Should I expect this?
>> 
>> Will this (to some extent) disappear in 2.8?
>> 
>
>This happen when the system fails to even open a real debug window. 
>Whatever you are doing, is causing debug windows to fail.  See Debugger
>class>>openContext:label:contents: and Object>>primitiveError:.  You can
>certainly modify primitiveError: to do something different, but just
>make sure it is safe and unlikely to fail!
>
>
>Hmm, it should also be posible to trigger this by having two threads
>fail at the same time.  This ought to be unusual, though, because of
>Squeak's non-preemptive threads.  (Unless, of course, you are using
>threads that run at different priorities).
>
>
>-Lex
>
>
>