STLink GDB Server discovery does not find CLT's STLink Server.

[schilkp]

Type: Bug Report

Describe the bug

• OS and Version: Manjaro 23.0.1
• VS Code Version: 1.82.0
• Embedded Tools Extension Version: v0.7.0
• Target embedded device: STM32L476
• RTOS version: NA

To Reproduce

• Install CubeCLT at the (default) location (/opt/st/stm32cubeclt), This will place the stlink gdbserver executeable at: /opt/st/stm32cubeclt/STLink-gdb-server/bin/ST-LINK_gdbserver
• Execute the following task:

  {
  "version": "2.0.0",
  "tasks": [
  {
    "label": "Test",
    "type": "shell",
    "command": "echo ${command:vscode-embedded.st.gdbserver}",
    "problemMatcher": []
  }
  ]
  }

Expected behavior The path of the st link gdb server is echoed into the terminal.

Actual behaviour Error: Could not find the path to "ST-Link_gdbserver". Ensure STM32CubeIDE is installed.

Additional context The debug message would indicate that vscode-embedded-tools is looking for the CubeIDE STLink gdbserver, as opposed to the CLT's. CubeIDE is also installed in the default location (/opt/st/stm32cubeide_1.13.1/), with it's gdb server at /opt/st/stm32cubeide_1.13.1/plugins/com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.linux64_2.1.0.202305091550/tools/bin/ST-LINK_gdbserver. According to previous changelogs this plugin should now be prioritizing the CLT version. Therefor the CubeIDE discovery is also likely broken. Furthermore, since CLT should be prioritized (according to your previous changelogs), the error message that CubeIDE should be installed is possibly wrong and misleading.

[trembel]

I can confirm this.

[funder7]

Same problem here, just configured the extension today on Linux.