Hi!
I wrote in another thread some time ago about getting this problem:
I have now fixed my test automation setup so I will not get this problem ordinarily. But, sometimes when I use the debugger manually, I do something that puts the debugger in this state anyway (e.g. when closing a Python process abruptly, giving it no chance to close the connection correctly).
When that happens, I have to unplug and replug the debugger to get it working again. This is OK when I run on my own computer, but sometimes I run things remotely on a computer on the other side of the office building...
Then, it would be nice to have some way to completely restart the debugger (in a manner similar to unplugging and replugging the USB cable) from the command-line, or some other program. Is there a convenient way to do this?
This is not a big and important problem, but it would be nice if it was possible.
Best regards,
Fabian
I wrote in another thread some time ago about getting this problem:
I have now fixed my test automation setup so I will not get this problem ordinarily. But, sometimes when I use the debugger manually, I do something that puts the debugger in this state anyway (e.g. when closing a Python process abruptly, giving it no chance to close the connection correctly).
When that happens, I have to unplug and replug the debugger to get it working again. This is OK when I run on my own computer, but sometimes I run things remotely on a computer on the other side of the office building...
Then, it would be nice to have some way to completely restart the debugger (in a manner similar to unplugging and replugging the USB cable) from the command-line, or some other program. Is there a convenient way to do this?
This is not a big and important problem, but it would be nice if it was possible.
Best regards,
Fabian