microsoft / microsoft/vscode-cpptools

Receiving AD7BreakpointErrorEvent when trying to re-enable breakpoint in VS Code while debuggin QNX app

Open
#12,115 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Environment
  • OS and version: Windows_NT x64 10.0.19045
  • VS Code: 1.87.1
  • C/C++ extension:1.3.0
  • OS and version of remote machine (if applicable):QNX qnx-vmware-x86 7.1.0
  • GDB / LLDB version:8.2.1
    Cpp_2
    Cpp_version
Bug Summary and Steps to Reproduce

Bug Summary:
Breakpoints can not be re-activated after being deactivated in VS Code when debugging a remote application on QNX

Steps to reproduce:

  1. In this environment:
    [Version: 1.87.1
    Commit: 1e790d77f81672c49be070e04474901747115651
    Date: 2024-03-06T00:21:36.258Z
    Electron: 27.3.2
    ElectronBuildId: 26836302
    Chromium: 118.0.5993.159
    Node.js: 18.17.1
    V8: 11.8.172.18-electron.0
    OS: Windows_NT x64 10.0.19045

  2. Do: the breakpoints are set before the application start. While the breakpoints are active - application stops on them. After the last active breakpoint was disabled - it is no longer possible to re-enable any of them, to add a new one or to pause the application.

  3. In the output - there is an "Send Event AD7BreakpointErrorEvent" reported. There are already similar error reports but the suggested solutions hasn't helped.
    DebugConsoleOutput.txt
    Cpp_2
    Cpp_version

Debugger Configurations
launch.json configuration
    "configurations": [
        {
            "name": "Application remote debug",
            "type": "cppdbg",
            "MIMode": "gdb",
            "miDebuggerPath": "C:/Users/user/qnx710/host/win64/x86_64/usr/bin/ntox86_64-gdb.exe",
            "targetArchitecture": "x86_64",
            "request": "launch",
            "program": "C:/Users/user`/ide-7.1-workspace/SUT/build/Application",
            "cwd": "${workspaceFolder}",
            "args": [],
            "environment": [],
            "stopAtEntry": false,
            "externalConsole": false,
            "launchCompleteCommand": "exec-run",
            "stopOnEntry": true,
            "setupCommands": [                       
                {
                    "description": "connect to the target's qconn",
                    "text": "target qnx 192.xxx.xxx.xxx:8000"
                },             
                {
                    "text": "set target-async off"
                },                         
               {
                    "description": "only set the executable (upload it before e.g. via SSH)",
                    "text": "set nto-executable /tmp/Application"               },
            ],            
            "logging": {
                "trace": true,
                "traceResponse": true,
                "engineLogging": true
            }
        },
Debugger Logs
Added the log as a file to the Bug Summary section
Other Extensions

No response

Additional Information

No response

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.

Research direction

Start with the attached DebugConsoleOutput.txt and the launch.json configuration, then reproduce the breakpoint disable and re-enable sequence against the stated QNX environment. Done means breakpoints can be re-enabled, new breakpoints can be added, and the application can be paused without the AD7BreakpointErrorEvent.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.