FS#35637 - [monodevelop] Could not connect to the debugger
Attached to Project:
Arch Linux
Opened by Pavlos Touboulidis (pav) - Tuesday, 04 June 2013, 09:54 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 25 October 2017, 16:32 GMT
Opened by Pavlos Touboulidis (pav) - Tuesday, 04 June 2013, 09:54 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 25 October 2017, 16:32 GMT
|
Details
For some time now, debugging with MonoDevelop does not work.
Trying to debug even the simplest console application gives
the following error:
"Could not connect to the debugger". "debugger-agent: Unable to connect to 127.0.0.1:40904" (port is random) Additional info: Sorry, I can't recall at what version this started happening but we're at 4.0.8-1 now. I don't think it's related to the version of mono that's installed, since I get the same error consistently with mono 2.9.10, 3.0.7 or 3.0.12 (git). And here's the output from the log file: ERROR [2013-06-04 12:36:18Z]: Error in debugger Mono.Debugging.Soft.ConnectionException: Could not connect to the debugger. ---> System.Net.Sockets.SocketException: interrupted at System.Net.Sockets.Socket.Accept () [0x0006d] in /build/mono/src/mono-3.0.7/mcs/class/System/System.Net.Sockets/Socket.cs:553 at Mono.Debugger.Soft.VirtualMachineManager.LaunchInternal (ITargetProcess p, System.Diagnostics.ProcessStartInfo info, System.Net.Sockets.Socket socket) [0x00004] in /build/monodevelop/src/monodevelop-4.0.8/main/contrib/Mono.Debugger.Soft/Mono.Debugger.Soft/VirtualMachineManager.cs:49 --- End of inner exception stack trace --- Steps to reproduce: * Start MonoDevelop * Open/create any C# application * Start debugging P.S. Someone else is having the same problem over at stackoverflow: http://stackoverflow.com/questions/16866207/unable-to-hit-breakpoints-in-monodevelop |
This task depends upon
Closed by Antonio Rojas (arojas)
Wednesday, 25 October 2017, 16:32 GMT
Reason for closing: Won't fix
Additional comments about closing: monodevelop has been dropped
Wednesday, 25 October 2017, 16:32 GMT
Reason for closing: Won't fix
Additional comments about closing: monodevelop has been dropped
Please change it to what you think is best and let's focus on the problem.
Can anyone reproduce this?
1) Install the xterm.
2) open a terminal and type:
$ Unset GNOME_DESKTOP_SESSION_ID
$ monodevelop
Worked with me.
Someone can make it permanent.