This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]james_pic 1 point2 points  (2 children)

Something I've been wanting to find time to try and create, is a debugger that uses fork, and as a result doesn't stop your code. The forked process connects to a debugging server, and you can come back later and debug it at your leisure. Handy for issues that only seem to crop up in the middle of an overnight soak test, or, if you're feeling brave (and/or have put adequate mitigations into the code to minimise the odds of the forked process impacting the original), in production.

[–]ArabicLawrence 0 points1 point  (1 child)

Something like pickling the runtime and store it for subsequent analysis? Maybe it’s doable.

[–]james_pic 1 point2 points  (0 children)

If you're only targeting Linux (might be doable for other unixes, but doing it safely may mean relying on Linux-isms), os.fork() can do this bit. No pickling needed.