ripdb icon indicating copy to clipboard operation
ripdb copied to clipboard

Exit debugger on disconnect?

Open WhyNotHugo opened this issue 8 years ago • 0 comments
trafficstars

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.

WhyNotHugo avatar Apr 06 '17 20:04 WhyNotHugo