https://bugzilla.novell.com/show_bug.cgi?id=646527
https://bugzilla.novell.com/show_bug.cgi?id=646527#c0 Summary: When Debugger Can't connect, socket seems to stay open Classification: Mono Product: MonoDroid Version: SVN Platform: x86-64 OS/Version: Windows 7 Status: NEW Severity: Normal Priority: P5 - None Component: Debugger AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.55 Safari/534.3 Without my device's wifi on, the first time on a fresh run of visual studio, if I go to debug, the app builds, gets copied over to device fine and then starts launching, but I just get a blank screen on my phone, and it eventually force closes. At this point I have to manually stop debugging, otherwise visual studio just hangs as if it is debugging, when it's really not. When I manually stop debugging I get the error: "The debugger was unable to terminate one or more processes: [N/A] MonoDroid: The debugger is still attaching to the process or the process is not currently executing the type of code selected for debugging. The debugger may be unstable now. It is recommended that you save all files and exit.". If I launch the app from the device after this, it launches fine. If I try debugging again from visual studio (without restarting visual studio), I get an error: "only one usage of each socket..." message, but then I can still manually launch the app on device (the new build of the app gets deployed to the device fine still). So it seems if the debugger fails to connect, it is still hanging in limbo and you can't bind the debugger again the next time you try (unless you restart visual studio), however the app still compiles fine and gets installed fine on device. Now, if I have wifi turned on, on my device, debugging works fine, and the whole process goes as expected. So, it looks to me like the debugging routine needs to be a bit more resilient in figuring out if it can't connect. Perhaps a simple timeout should be implemented, and if the device does not attach to the debugger in a reasonable amount of time (and in this case, a useful error message should be displayed to the user suggesting to check their wifi, etc.), the debugger should cleanly quit. Also, if I force stop debugging, it should quit cleanly enough that I don't have to restart visual studio to try debugging again. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
