-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
Disconnecting from the debugger (eg: closing nc) will just leave the debugged application frozen (and I can't connect back!). This is probably a result of never continue'ing the execution, but ripdb doesn't listen for new connections either.
I've to remember to c or q before disconnecting.
There are probably two fixes for this:
quitafter a remote connection disconnects from the debugger.- After a disconnection is made, start listening for new connections (so we can log back in and
quit/continuemanually).
IMHO, the first option is what's most intuitive to users, so if I hit ctrl+d on nc or anything alike, it does the same as a doing that in ipdb.
ckaraneen
Metadata
Metadata
Assignees
Labels
No labels