[squeak-dev] Regression | Cannot interrupt "[  repeat ] fork" anymore
Christoph.Thiede at student.hpi.uni-potsdam.de
Thu Dec 16 18:29:30 UTC 2021
Hi Dave, hi Marcel,
one "recent" change I noticed is that one to SmalltalkImage>>#processPreemptionYields by Dave in May, which answered false before but answers true since then. But this is just an observation, I do not know whether this change was justified by a change on the VM side.
> even if CMD+Dot interrupts the "[  repeat ] fork" from the interrupt watcher
How did you achieve to do this? The interrupt doesn't work for me in this situation.
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Taeumel, Marcel
Gesendet: Donnerstag, 16. Dezember 2021 15:53:37
Betreff: Re: [squeak-dev] Regression | Cannot interrupt "[  repeat ] fork" anymore
Hi Christoph, hi Dave, hi all --
"Processor preemptedProcess" does not behave as it used to be. It now answers the current ui process even if CMD+Dot interrupts the "[  repeat ] fork" from the interrupt watcher.
Maybe you can spot the issue right away?
ProcessorScheduler >> preemptedProcess
"Return the process that the currently active process just preempted."
self activeProcess priority to: 1 by: -1 do: [:priority |
(quiescentProcessLists at: priority) ifNotEmpty: [:list |
^ Smalltalk processPreemptionYields
ifTrue: [list last]
ifFalse: [list first]]].
Am 16.12.2021 14:33:51 schrieb David T. Lewis <lewis at mail.msen.com>:
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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev