Skip to content

Exit debugger on disconnect? #4

@WhyNotHugo

Description

@WhyNotHugo

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions