On Thu, Dec 16, 2021 at 11:27:09AM +0100, Marcel Taeumel wrote:
> Hi all --
> 
> I am investigating a?? regression revealed via DebuggerTests >> test01UserInterrupt. One cannot interrupt "[ [] repeat ] fork" from a do-it anymore. :-(
> 
> VM: 202112022203 (32-bit, Windows 10)
> 
> Update: #20872
> 
> Since the forked process should run at priority 40 and the "user interrupt watcher" watches at priority 60, this must work. Did we loose a process scheduling point in "[] repeat"? It's still implemented as "[self value. true] whileTrue".
> 

Confirming on Linux and also on an interpreter VM with trunk level V3 image,
so the issue is in the image, not the VM.

Dave