Not working on vscode 1.59.0, "Cannot read property 'port' of null"

cob258

I recently couldn't debug program using vscode, when I press run a message box tells me "Cannot read property 'port' of null" and suggests to "Open 'launch.json'", even if I add "port":"3333" to the config the problem is not solved.

My vscode version is 1.59.0, I tried the same setup on vscode 1.54.3 and it worked, maybe the update broke something?

Waiting for your reply,
Regards.

admin

cob258

Please show the content of launch.json

It works fine on my pc, maybe you need reinstall stm8-debug !

cob258

Thanks for replying, here is the launch.json file

{
    // 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": [
        {
            "type": "stm8-debug",
            "request": "launch",
            "name": "stm8 debug",
            "serverType": "stm8-sdcc",
            "openOcdConfigs": [
                "interface/stlink.cfg",
                "target/stm8s207.cfg"
            ],
            "executable": "${workspaceRoot}\\build\\main.elf",
            "cpu": "STM8S207RB"
        },        
    ]
}

note : I run openocd manually from the terminal, the stm8s207.cfg is not included by default in openocd package, I added it later, but it works fine

It works fine on my pc, maybe you need reinstall stm8-debug !

I tried reinstalling the latest version or even older ones but still the same problem

admin

cob258

For port property, we have default value, even setting it to null does not cause this error
This debugger(v1.4.1) will auto create a openocd instance, if you create it manual, maybe occur port conflicts.
If you want use custom xxx.cfg files, you have 2 methods：
1. Add your cfg file to C:\Users\<YOUR USER NAME>\.vscode\extensions\cl.stm8-debug-1.4.1\bin\openocd\scripts
2. Use absolute path in openOcdConfigs property

========================

I honestly don't know the cause of this problem, my vscode version is also v1.59.0.

maybe other debugger extensions are causing this problem