Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exit debugger on disconnect? #4

Open
WhyNotHugo opened this issue Apr 6, 2017 · 0 comments
Open

Exit debugger on disconnect? #4

WhyNotHugo opened this issue Apr 6, 2017 · 0 comments

Comments

@WhyNotHugo
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant