microsoft / microsoft/vscode-cpptools

Failed To Parse Processes

Open
#11,371 1 comment 0 reactions 1 assignee View on GitHub

@xisui-MSFT is already working on this.

Since Sep 1, 2023.

embedded
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Environment
  • OS and version: Windows 11 [Version 10.0.22621.2134]
  • VS Code: 1.81.1 (User Setup)
  • C/C++ extension: 1.17.4
  • OS and version of remote machine (if applicable): Horizon (Nintendo 3DS / 11.17.0-50U)
  • GDB / LLDB version: 13.2
Bug Summary and Steps to Reproduce

Bug Summary:
I'm trying to get the list of remote processes but the debugger fails to process them.

Steps to reproduce:
Setting up the steps to reproduce is a bit of a hassle for everyone else because you need to have custom firmware on a Nintendo 3DS and set everything up.

It's as simple as using the provided configuration and getting an error back. I've confirmed that doing info os processes within gdb while attached has provided me the remote processes. This does not work with vscode.

Debugger Configurations
{
    "version": "0.2.0",
    "configurations": [
    {
        "name": "devkitARM GDB",
        "type": "cppdbg",
        "request": "attach",
        "program": "${workspaceRoot}/build/lovepotion.elf",
        "MIMode": "gdb",
        "windows": {
            "miDebuggerPath": "C:/msys64/opt/devkitpro/devkitARM/bin/arm-none-eabi-gdb",
        },
        "linux": {
            "miDebuggerPath": "/opt/devkitpro/devkitARM/bin/arm-none-eabi-gdb"
        },
        "miDebuggerServerAddress": "192.168.50.29:4000",
        "useExtendedRemote": true,
        "setupCommands": [
            {
                "description": "pretty printing",
                "text": "-enable-pretty-printing",
                "ignoreFailures": true
            },
            {
                "description": "hex",
                "text": "-gdb-set output-radix 16",
                "ignoreFailures": true
            }
        ],
        "processId": "${command:pickRemoteProcess}"
    },
}
Debugger Logs
N/A
Other Extensions

Name: CMake
Id: twxs.cmake
Description: CMake langage support for Visual Studio Code
Version: 0.0.17
Publisher: twxs
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=twxs.cmake

Name: GitHub Pull Requests and Issues
Id: GitHub.vscode-pull-request-github
Description: Pull Request and Issue Provider for GitHub
Version: 0.70.0
Publisher: GitHub
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github

Name: Hex Editor
Id: ms-vscode.hexeditor
Description: Allows viewing and editing files in a hex editor
Version: 1.9.12
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-vscode.hexeditor

Name: Material Icon Theme
Id: PKief.material-icon-theme
Description: Material Design Icons for Visual Studio Code
Version: 4.30.0
Publisher: Philipp Kief
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=PKief.material-icon-theme

Name: pica200
Id: ian-h-chamberlain.pica200
Description: Syntax highlighting for the Pica200 shader language
Version: 0.1.0
Publisher: ian-h-chamberlain
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ian-h-chamberlain.pica200

Name: Shader languages support for VS Code
Id: slevesque.shader
Description: Syntax highlighter for shader language (hlsl, glsl, cg)
Version: 1.1.5
Publisher: slevesque
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=slevesque.shader

Name: TODO Highlight v2
Id: jgclark.vscode-todo-highlight
Description: highlight TODOs, FIXMEs, and any keywords, annotations...
Version: 2.0.8
Publisher: Jonathan Clark
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=jgclark.vscode-todo-highlight

This issue would not be impacted by any of these extensions.

Additional Information

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.