[Mono-bugs] [Bug 670164] New: Debugger can't be immediately started just after a previous session is done

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=670164

https://bugzilla.novell.com/show_bug.cgi?id=670164#c0


           Summary: Debugger can't be immediately started just after a
                    previous session is done
    Classification: Mono
           Product: MonoDroid
           Version: SVN
          Platform: i686
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Debugger
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: calberto.cortez at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Invoking the debugger to start a new session just after a previous one is done
is causing the runtime to exit (in logcat we only get 'activity exited
cleanly').

After some research, it seems to be that the culprit is in
mini/debugger-agent.c, specifically in line 1107, in the transport_connect()
function:


                conn_fd = accept (sfd, NULL, NULL);
                if (conn_fd == -1) {
                        fprintf (stderr, "debugger-agent: Unable to listen on
%s:%d\n", host, port);
                        exit (1);
                }


It seems that the previous call to bind() in the same function is failing with
a EADDRINUSE error, since the port is still busy -from the previous debug
session-, and thus we need to wait around 1 minute for the port to 'unbind'
itself.


Kankaroo mentioned this may be handled from the MD MDr stack, but I'm filling
this bug so we keep track of this issue.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.