Hi all!

Christoph put in a lot of effort to figure out the cause of infinite debugger chains under various circumstances. He is curious how far "debugging the debugger" can work and how possible improvements to code simulation might look like.

We basically figured out that the debugger that pops up from an unhandled error (or warning) must never try debugging a simulated process but always the "genuine process", which is the one that is actually running and which may do the code simulation for another process.

Please find attached a change set with that fix. Tests are in "DebuggerTests" and "ProcessTest". The most interesting methods are ProcessorScheduler >> #debugContext:title:full:contents: and Process >> #debugWithTitle:full:contents:. Please take a look at their comments.


We will merge this into Trunk in a some days, given that there are no objections. :-)

Related discussions:
http://forum.world.st/I-broke-the-debugger-tp5110752p5110814.html [http://forum.world.st/I-broke-the-debugger-tp5110752p5110814.html]

http://forum.world.st/The-Inbox-Morphic-ct-1610-mcz-tp5108228.html [http://forum.world.st/The-Inbox-Morphic-ct-1610-mcz-tp5108228.html]


Best,
Marcel and Christoph

P.S.: Debugging a dialog invocation looks nicer now. Try it out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210311/734479d4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 13738 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210311/734479d4/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: use-genuine-process-to-fix-simulation.2.cs
Type: application/octet-stream
Size: 35325 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210311/734479d4/attachment.obj>