Hi Christoph,


> On Mar 4, 2021, at 3:08 AM, Thiede, Christoph <Christoph.Thiede at student.hpi.uni-potsdam.de> wrote:
> 
> 
> Hi Jaromir,
> 
> 
> 
> thanks for your report. There are two problems here:
> 
> 
> 
> 1. The usage of primitive 19 in #newProcess, which I'm glad not to be the only person to find it questionary. I already mentioned this here: http://forum.world.st/Just-another-debugger-bug-primitive-19-td5109411.html IMO the primitive does not make sense in this place, rather we should raise the simulation guard when primitiveSuspend or primitiveResume is invoked via simulation. Still, it is not necessarily a bad thing to let these things happen during simulation - that's why I would prefer to show some confirmation dialog instead of a warning. This is already on my to-do list and a solution for the second aspect should arrive in the Trunk during the next weeks. :-)
> 

Good to hear.  And your point about it not making sense makes me think.  Given fast step, whether one hits the simulation guard or not doesn’t depend on whether one is debugging, but depends on whether one is at just the right point to enter doPrimitive:... rather than just perform:.

So I agree; we should nuke it, with one proviso.  We need to ensure that a newProcess gets Processor activePriority.  ie we need to ensure that Processor activeProcess is always correct.  Some more thought on this is needed.
> 
> 2. Debugger chains crashing your image, which has already been discussed in great detail in http://forum.world.st/I-broke-the-debugger-td5110752.html#a5124736. I found the cause of the issue and have provided two possible solutions in this thread. Marcel and I are currently discussing the last details of the patch, but it should be complete soon and will arrive in the Trunk, probably together with the extended simulation guard as noted above!
> 
> 
> 
> If you find further interesting bugs, please let us know them all. :D
> 
> 
> 
> Best,
> 
> Christoph
> 
> Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Jaromir Matas <m at jaromir.net>
> Gesendet: Donnerstag, 4. März 2021 10:03:13
> An: squeak-dev at lists.squeakfoundation.org
> Betreff: [squeak-dev] Simulation guard <primitive: 19> crashes the image
>  
> Hi, why the simulation guard <primitive: 19> in BlockClosure >> newProcess?
> 
> It crashes the image when debugging e.g. [] fork. You hit Into -> Into ->
> the the error window pops up, you cancel it (or Abandon...) and hit Into
> again and the image is done :|
> 
> In case there's no reason to keep the simulation guard why not just remove
> it?
> Thanks,
> 
> Squeak6.0alpha-20243-64bit-202003021730-Windows
> 
> 
> 
> -----
> ^[^ Jaromir
> --
> Sent from: http://forum.world.st/Squeak-Dev-f45488.html
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210304/7d6c38a8/attachment.html>