You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
quit after 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/continue manually).
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.
The text was updated successfully, but these errors were encountered:
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 nevercontinue
'ing the execution, butripdb
doesn't listen for new connections either.I've to remember to c or q before disconnecting.
There are probably two fixes for this:
quit
after a remote connection disconnects from the debugger.quit
/continue
manually).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 inipdb
.The text was updated successfully, but these errors were encountered: