search

ARM-software / vscode-arm-debugger

https://marketplace.visualstudio.com/items?itemName=Arm.arm-debugger
Other
6 stars 0 forks source link

Arm Debugger freezes #4

Open Aptahar opened 5 months ago

Aptahar commented 5 months ago

Type: Bug Report

Describe the bug

To Reproduce Steps to reproduce the behavior:

  1. Debug starts and work normaly
  2. At some point when do 'Step Into' command, Debugger freezes with message in DEBUG CONSOLE (see Screenshot1)
  3. After that Target stay in Run mode and doesn't respond to any buttons: Pause, Restart, Stop
  4. Restart button clear DEBUG CONSOLE
  5. After some time later (few seconds) button Stop can stop Debugging, but not every time, some times only restart VScode is the solution.
  6. Button Pause cause notification like on Screenshot2

Code samples and logs Where are any logs can be finded?

tasks.json

{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "arm-debugger.flash",
            "serialNumber": "${command:device-manager.getSerialNumber}",
            "program": "${command:arm-debugger.getApplicationFile}",
            "cmsisPack": "${command:device-manager.getDevicePack}",
            "deviceName": "${command:cmsis-csolution.getDeviceName}",
            "processorName": "${command:cmsis-csolution.getProcessorName}",
            "problemMatcher": [],
            "label": "Flash Device"
        },
        {
            "type": "shell",
            "label": "generate fw",
            "command": "./utils/generate_firmware_VScode.sh",
            "problemMatcher": [],
            "group": {
                "kind": "build",
                "isDefault": true
            }
        }
    ]
}

Screenshots Screenshot1: image Screenshot2: image

Aptahar commented 5 months ago

After another restart VScode have this message:
image

Aptahar commented 5 months ago

debugger fails in irq handlers

thegecko commented 5 months ago

This popup message occurs when an existing armdbg process exists, often if it hasn't been terminated correctly. We are investigating this. Killing any armdbg/java processes (or rebooting) will fix this issue on the meantime.