Unwanted information output when issuing commands in Debug Console

[davepregan]

Unexpected behavior
When issuing GDB commands in the Debug Console a message of the form below is output after the information
{"output":"","token":31,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[]}}

I have commented out showDevDebugOutput in my launch.json in an attempt to remove this

Expected behavior
GDB commands can be handled in the Debug Console without this message

Screenshots

Environment:

• Cortex-Debug Version: 1.12.1
• OS: Windows 11
• GDB Version: GNU gdb (GNU Tools for STM32 14.3.rel1.20251027-0700) 15.2.90.20241229-git
• Compiler Toolchain Version: arm-none-eabi-gcc.exe (GNU Tools for STM32 14.3.rel1.20251027-0700) 14.3.1 20250623

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": "Debug Microcontroller - STLink-V3",
            "cwd": "${workspaceFolder}",        //Path from where commands are executed
            "type": "cortex-debug",             //Debug 
            "executable": "${command:cmake.launchTargetPath}", //or fixed file path: build/project-name.elf
            "request": "launch",                //Use "attach" to connect to target w/o elf download
            "servertype": "stlink",             //Use stlink setup of cortex-M debug
            "serverArgs": [
                "-s",
                "-m", "0",
                "-k",
                "--frequency", "21000",
                "-el", "${workspaceFolder}\\..\\..\\SupportProjects\\MT25Q128A_STM32F746_KAL_AB\\MT25Q128A_STM32F746_KAL_AB.stldr"
            ],
            "gdbPath": "c:/ST/STM32CubeIDE_1.16.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.14.3.rel1.win32_1.0.100.202602081740/tools/bin/arm-none-eabi-gdb.exe",
            "device": "STM32F746",            //MCU used
            "interface": "swd",                 //Interface setup
            "serialNumber": "0051003D3234510533353533",                 //Set ST-Link ID if you use multiple at the same time
            "runToEntryPoint": "main",          //Run to main and stop there
            "v1": false,
            // "showDevDebugOutput": "raw",
           "svdFile": "c:/ST/STM32CubeIDE_1.16.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.productdb.debug_2.2.400.202601091600/resources/cmsis/STMicroelectronics_CMSIS_SVD/STM32F746.svd",
            "serverpath": "C:\\ST\\STM32CubeIDE_1.16.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.400.202601091506\\tools\\bin\\ST-LINK_gdbserver.exe",
            "armToolchainPath": "c:\\ST\\STM32CubeIDE_1.16.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.400.202601091506\\tools\\bin",
            "stm32cubeprogrammer": "c:\\Program Files\\STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin"
        },
        {
            "name": "Debug Attach mcu",
            "cwd": "${workspaceFolder}",        //Path from where commands are executed
            "type": "cortex-debug",             //Debug 
            "executable": "${command:cmake.launchTargetPath}", //or fixed file path: build/project-name.elf
            "request": "attach",                //Use "attach" to connect to target w/o elf download
            "servertype": "stlink",             //Use stlink setup of cortex-M debug
            "serverArgs": [
                "-s",
                "-m", "0",
                "-k",
                "--frequency", "21000",
                "-el", "${workspaceFolder}\\..\\..\\SupportProjects\\MT25Q128A_STM32F746_KAL_AB\\MT25Q128A_STM32F746_KAL_AB.stldr"
            ],
            "device": "STM32F746",            //MCU used
            "interface": "swd",                 //Interface setup
            "serialNumber": "004C003C3331510833323639",                 //Set ST-Link ID if you use multiple at the same time
            "runToEntryPoint": "main",          //Run to main and stop there
            "svdFile": "{env:STM32F746SVDPath}",         //SVD file to see reisters
            // C:\\ST\\STM32CubeIDE_1.15.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.productdb.debug_2.1.200.202403061128\\resources\\cmsis\\STMicroelectronics_CMSIS_SVD\\STM32F746.svd
            "v1": false,
            "showDevDebugOutput": "raw",

            /* Will get automatically detected if STM32CubeIDE is installed to default directory
               or it can be manually provided if necessary via the setDebugEnvVars.bat in /scripts .. */
            "serverpath": "${env:serverpath}",
            //c:\\ST\\STM32CubeIDE_1.15.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.1.200.202401191126\\tools\\bin\\ST-LINK_gdbserver.exe
            "armToolchainPath": "${env:armToolchainPath}",
            //c:\\ST\\STM32CubeIDE_1.15.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.0.100.202403111256\\tools\\bin
            "stm32cubeprogrammer": "${env:stm32cubeprogrammer}",
            //c:\\Program Files\\STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin

            /* If you use external loader, add additional arguments */
            //"serverArgs": ["--extload", "path/to/ext/loader.stldr"]
        },
        {
            "name": "VCU UT Debug",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/build/tests/Debug/tests/vcu_test.exe",
            "args": [],
            "stopAtEntry": true,
            "cwd": "${fileDirname}",
            "environment": [],
            "externalConsole": true,
            "MIMode": "gdb",
            "miDebuggerPath": "C:/msys64/mingw64/bin/gdb.exe",
            "setupCommands": [
            {
                "description": "Enable pretty-printing for gdb",
                "text": "-enable-pretty-printing",
                "ignoreFailures": true
            },
            {
                "description": "Set Disassembly Flavor to Intel",
                "text": "-gdb-set disassembly-flavor intel",
                "ignoreFailures": true
            }
            ]
        }
    ]
}

Text from Debug Console
Attached as file

cortex_debug_dump.txt

[haneefdm]

Could you check again? In the file cortex_debug_dump.txt, I see the the following

    "request": "launch",
    "showDevDebugOutput": "raw",
    "pvtShowDevDebugOutput": "raw"

The pvtShowDevDebugOutput is the one we save from your original debug config. It is set to raw. Although the launch.json you provided has it commented out for "launch". VSCode also saves all files before launching

We do modify the showDevDebugOutput when we process you debug config and that is why we copy your originval setting to pvtShowDevDebugOutput so we know what the original value was.

I am at a loss. You did everything right. Could I ask you to make sure your launch.json correct and saved, restart VSCode and try again. I know it sounds stupid but I don't know what to try. Please make sure you are not using "attach" config because over there it is indeed enabled (set to "raw") but from your screenshot I can see that you are NOT using "attach". We don't look at your launch.json We are given your exact selected config by VSCode.

[davepregan]

cortex_debug_dump_no_raw.txt

Apologies for the confusion. The advice on posting said to enable raw, which I did for the dump. The raw is now disabled.
You can see from the screenshot that it is not using the attach condiguration.

The message is still produced

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": "Debug Microcontroller - STLink-V3",
            "cwd": "${workspaceFolder}",        //Path from where commands are executed
            "type": "cortex-debug",             //Debug 
            "executable": "${command:cmake.launchTargetPath}", //or fixed file path: build/project-name.elf
            "request": "launch",                //Use "attach" to connect to target w/o elf download
            "servertype": "stlink",             //Use stlink setup of cortex-M debug
            "serverArgs": [
                "-s",
                "-m", "0",
                "-k",
                "--frequency", "21000",
                "-el", "${workspaceFolder}\\..\\..\\SupportProjects\\MT25Q128A_STM32F746_KAL_AB\\MT25Q128A_STM32F746_KAL_AB.stldr"
            ],
            "gdbPath": "c:/ST/STM32CubeIDE_1.16.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.14.3.rel1.win32_1.0.100.202602081740/tools/bin/arm-none-eabi-gdb.exe",
            "device": "STM32F746",            //MCU used
            "interface": "swd",                 //Interface setup
            "serialNumber": "0051003D3234510533353533",                 //Set ST-Link ID if you use multiple at the same time
            "runToEntryPoint": "main",          //Run to main and stop there
            "v1": false,
            // "showDevDebugOutput": "raw",
           "svdFile": "c:/ST/STM32CubeIDE_1.16.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.productdb.debug_2.2.400.202601091600/resources/cmsis/STMicroelectronics_CMSIS_SVD/STM32F746.svd",
            "serverpath": "C:\\ST\\STM32CubeIDE_1.16.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.400.202601091506\\tools\\bin\\ST-LINK_gdbserver.exe",
            "armToolchainPath": "c:\\ST\\STM32CubeIDE_1.16.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.400.202601091506\\tools\\bin",
            "stm32cubeprogrammer": "c:\\Program Files\\STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin"
        },
        {
            "name": "Debug Attach mcu",
            "cwd": "${workspaceFolder}",        //Path from where commands are executed
            "type": "cortex-debug",             //Debug 
            "executable": "${command:cmake.launchTargetPath}", //or fixed file path: build/project-name.elf
            "request": "attach",                //Use "attach" to connect to target w/o elf download
            "servertype": "stlink",             //Use stlink setup of cortex-M debug
            "serverArgs": [
                "-s",
                "-m", "0",
                "-k",
                "--frequency", "21000",
                "-el", "${workspaceFolder}\\..\\..\\SupportProjects\\MT25Q128A_STM32F746_KAL_AB\\MT25Q128A_STM32F746_KAL_AB.stldr"
            ],
            "device": "STM32F746",            //MCU used
            "interface": "swd",                 //Interface setup
            "serialNumber": "004C003C3331510833323639",                 //Set ST-Link ID if you use multiple at the same time
            "runToEntryPoint": "main",          //Run to main and stop there
            "svdFile": "{env:STM32F746SVDPath}",         //SVD file to see reisters
            // C:\\ST\\STM32CubeIDE_1.15.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.productdb.debug_2.1.200.202403061128\\resources\\cmsis\\STMicroelectronics_CMSIS_SVD\\STM32F746.svd
            "v1": false,
            "showDevDebugOutput": "raw",

            /* Will get automatically detected if STM32CubeIDE is installed to default directory
               or it can be manually provided if necessary via the setDebugEnvVars.bat in /scripts .. */
            "serverpath": "${env:serverpath}",
            //c:\\ST\\STM32CubeIDE_1.15.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.1.200.202401191126\\tools\\bin\\ST-LINK_gdbserver.exe
            "armToolchainPath": "${env:armToolchainPath}",
            //c:\\ST\\STM32CubeIDE_1.15.0\\STM32CubeIDE\\plugins\\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.0.100.202403111256\\tools\\bin
            "stm32cubeprogrammer": "${env:stm32cubeprogrammer}",
            //c:\\Program Files\\STMicroelectronics\\STM32Cube\\STM32CubeProgrammer\\bin

            /* If you use external loader, add additional arguments */
            //"serverArgs": ["--extload", "path/to/ext/loader.stldr"]
        },
        {
            "name": "VCU UT Debug",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/build/tests/Debug/tests/vcu_test.exe",
            "args": [],
            "stopAtEntry": true,
            "cwd": "${fileDirname}",
            "environment": [],
            "externalConsole": true,
            "MIMode": "gdb",
            "miDebuggerPath": "C:/msys64/mingw64/bin/gdb.exe",
            "setupCommands": [
            {
                "description": "Enable pretty-printing for gdb",
                "text": "-enable-pretty-printing",
                "ignoreFailures": true
            },
            {
                "description": "Set Disassembly Flavor to Intel",
                "text": "-gdb-set disassembly-flavor intel",
                "ignoreFailures": true
            }
            ]
        }
    ]
}

[haneefdm]

Okay, now that makes sense. I will look into it. Can you do me a favor though? Could you install the following pre-release to see if the problem still exists?

https://github.com/Marus/cortex-debug/releases

[davepregan]

I upgraded as requested. The same result

[haneefdm]

Yup, I see it. It was vscode that was printing the output. We did not realize it was doing that. It will be fixed in the next pre-release

[davepregan]

Great. Thanks