v0.6.0 Broke Arduino debugging

[zfields]

My debug configuration for Arduino has worked since the inception of this extension. With version 0.6.0 arduino is no longer a valid type for debug configuration.

I confirmed the regression by downgrading to v0.5.0 and everything works as expected.

launch.json:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Arduino",
            "type": "arduino",
            "request": "launch",
            "program": "${file}",
            "cwd": "${workspaceFolder}",
            "MIMode": "gdb",
            "targetArchitecture": "arm",
            "miDebuggerPath": "",
            "debugServerPath": "/usr/bin/openocd",
            "debugServerArgs": "-f interface/stlink.cfg -f target/stm32l4x.cfg",
            "customLaunchSetupCommands": [
                {
                    "text": "target extended-remote localhost:3333"
                },
                {
                    "text": "file \"${file}\""
                },
                {
                    "text": "load"
                },
                {
                    "text": "monitor reset halt"
                },
                {
                    "text": "monitor reset init"
                }
            ],
            "stopAtEntry": true,
            "serverStarted": "Info\\ :\\ [\\w\\d\\.]*:\\ hardware",
            "launchCompleteCommand": "exec-continue",
            "filterStderr": true,
            "args": []
        }
    ]
}

[fredsa]

I can confirm that building extension from source against tag v0.5.0 makes the 'Arduino' option appear for launch/debug configs.

Unfortunately, my board is not supported for debugging, so I couldn't test beyond verifying the 'Arduino' option does appear as expected.

[Tnthr]

#1610

It seems the developers purposely removed support for debugging in the latest version. You can see the change in the linked issue above. I agree it seems like a regression but I guess they are waiting for someone to be a bit more active in the developing/maintaining of that portion of the extension.