Hi Jakob,

That would be an awsome feature :) At the moment I insert self halt at the beginning of the forked process which works but is sort of a nuisance… Unfortunately I know very little about debugger’s implementation so far but I love the idea! (especially for a beginner, figuring out how to debug a forked process is a nightmare – well, at least for me it was)
Thanks,
jaromir

From: Jakob Reschke<mailto:jakres+squeak at gmail.com>
Sent: Saturday, January 22, 2022 11:47
To: squeak-dev at lists.squeakfoundation.org<mailto:squeak-dev at lists.squeakfoundation.org>
Subject: [squeak-dev] Debugging through #fork

Dear Squeakers,

I was just asking myself, why we cannot debug process forking like this:

0. In the Debugger: [ self doSomething ] "--> next send" fork. nextStatement.
1. Press the Through button.
2. The debugger stops at the next step after the send of #fork: [ self
doSomething ] fork. "-->" nextStatement.
3. A second full debugger opens on the new (and now suspended)
process: [ self "-->" doSomething ] fork. nextStatement.

Do you see any drawbacks or huge implementation challenges or
blockers? Or would it be "only" a matter of somebody finding the time
and will to implement such a feature?

Kind regards,
Jakob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220122/7bc2c2ff/attachment.html>