Debugger.Launch not working on MacOS

[thepalbi]

Description

A few days ago, while playing around with Coyote I find out there was an issue while using a command that supposedly launches a debugger, and wait until you attach it to continue execution. This feature is not working in MacOS, but they suggested trying adding a

Debugger.Launch()

to trigger the debugging. This is also not working in MacOS (when running a program directly from the CLI). However, I'm able to debug from VS. Also checked, and the call to Debugger.Launch is returning true, as if it executed correctly.

Is it possible there's no support for this use-case in MacOS?

Also tried this small program:

namespace Microsoft.Coyote.Samples.HelloWorldTasks
{
    public static class Program
    {
        public static void Main()
        {
            bool debuggerLaunchSuccessful = Debugger.Launch();
            if (!debuggerLaunchSuccessful)
            {
                Console.WriteLine("Debugger launch not successful 😐");
            }

            Console.WriteLine("Program finished correctly");
        }
    }
}

And still getting not the expected behavior. Tried both with dotnet run, and building a standalone.

Configuration

➜  HelloWorldTasks git:(master) ✗ dotnet --version
3.1.401

• MacOS 10.15.5

Regression?

Other information

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

[svick]

If I'm following the code right, Debugger.Launch() on Unix ends up here:

runtime/src/coreclr/src/debug/ee/debugger.cpp

Lines 7057 to 7059 in 383295b

	#else // !TARGET_UNIX
	return E_ABORT;
	#endif // !TARGET_UNIX

I.e. it does nothing, it only fails.

Debugger.Launch() returns true, because it almost always does, even in the case of a failure:

runtime/src/coreclr/src/debug/ee/debugger.cpp

Lines 6711 to 6716 in 383295b

	if (!IsDebuggerPresent())
	{
	LOG((LF_CORDB, LL_ERROR, "D::LDFU: Failed to launch the debugger.\n"));
	}
	return S_OK;

[thepalbi]

Thanks for the clarification. Left a note that this is not supported on Linux or MacOS, and ended up debugging by creating a custom Run Configuration on VS.

[danmoseley]

@thepalbi you can click the pencil in the top right of the documentation topic to fix stuff like this -- I did it in this case.