hi, i just discovered that Halt signals the exception as unhandled one..
which, in own turn makes announcers who using on:fork: to _fork_ the process, so when debugger opens you don't see who sent the announcement since the bottom stack frame is #on:fork:
Excellent this would also explains some strange behavior we got when putting halt in repackage tests.
Now if you change
Halt>>defaultAction
^ UIManager default unhandledErrorDefaultAction: self
" UnhandledError signalForException: self "
things is much better, since i can see whole stackâ¦
Can you open a bug entry? and I will handle it once I authorize myself to hack.
I find it strange, why to open debugger with halt, one must signal other exception (which is UnhandledError)?
I did not get the previous sentence but you will explain it to me. When I put halt in the code I want to get a chance to open a debugger?
UnhandledError ~~ Halt!!!