Just a quick random thought before it gets away...
It would be *nice* if when debugging and I step over a fork, the new
process automatically halts at the start and spawns a new debugger.
If its it was spawned at a higher priority, I could immediately move
to the new debugger and step through before returning the original
debugger. This would help a lot when stepping through unit tests that
to test exotic corner cases are sometimes needfully convoluted about
which order the processes run. Maybe if somehow a Process new it was
being debugged and the new process inherited that state.
cheers -ben
Maybe if somehow a Process new it was
being debugged and the new process inherited that state.
I plan to introduce inheriting state for spawn processes. Idea is to add InheritedProcessSpecificVariable.
Particularly I want mark processes which was forked during test execution and maybe manage it automatically: terminating on test completion, collecting failures as additional test result.
Maybe
if somehow a Process new it was
being debugged and the new process inherited that state.
I plan to introduce inheriting state for spawn processes. Idea
is to add InheritedProcessSpecificVariable.
Particularly I want mark processes
which was forked during test execution and maybe manage it
automatically: terminating on test completion, collecting
failures as additional test result.