Closed mgedmin closed 14 years ago
Yeah that's weird...in my own tests it sometimes hangs...I'm setting socket.setdefaulttimeout(5), but sometimes it doesn't catch it?
Anyway, I pushed up a fix, which sets the timeout on the specific socket.
Yep, it's fixed. If I try ":Dbg b' now, I get a "waiting for connection" message and then it goes away in a few seconds and I can use vim again.
I tried to use ':Dbg b' to set a breakpoint in a Python file without first starting the debugger with ':Dbg .'. I got a browser window to a nonexistent URL and the gvim instance froze. There's no reaction to Ctrl-C. I had to kill my vim.