fork during debugging to auto spawn new debugger
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
Hi Ben 2016-02-23 14:08 GMT+01:00 Ben Coman <btc@openinworld.com>:
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.
Le 23/2/16 15:14, Denis Kudriashov a écrit :
Hi Ben
2016-02-23 14:08 GMT+01:00 Ben Coman <btc@openinworld.com <mailto:btc@openinworld.com>>:
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.
oh yes !!
participants (3)
-
Ben Coman -
Denis Kudriashov -
stepharo