microsoft / microsoft/vscode-cpptools

[ARM] stopAtEntry: false has no effect

Open
#978 8 comments 0 reactions 1 assignee View on GitHub

@pieandcakes is already working on this.

Since Aug 17, 2017.

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

Description

Here is:
VSCode 1.15.1 / x64
cpptools 0.12.2
Windows 8/x64
I am debugging remote target (ARM MCU) using arm-gcc tools and openocd server.

launch.json:

{
   "version": "0.2.0",
   "configurations": 
   [
      {
         "name": "OpenOCD & gdb",
         "type": "cppdbg",
         "request": "launch",
         "program": "${workspaceRoot}/Debug/Main.elf",
         "args": [],
         "stopAtEntry": false,
         "cwd": "${workspaceRoot}",
         "environment": [],
         "externalConsole": false,
         "visualizerFile": "${workspaceRoot}/Neon.natvis",
         "showDisplayString": true,
         "logging": 
         {
            "engineLogging":true,
            "moduleLoad": false,
            "exceptions": false,
            "trace": false, 
            "traceResponse": false
         },
         //"preLaunchTask": "oocd",
         "windows": 
         {
            "MIMode": "gdb",
            "miDebuggerPath":"c:/arm/bin/arm-none-eabi-gdb.exe",     
            "setupCommands": 
            [
               {"text":"target remote localhost:3333"},
               {"text":"monitor reset halt"},
               {"text":"monitor halt"},
               {"text":"set var {int}0xE0042008 |= 0x000001FF"},
               {"text":"set var {int}0xE004200C |= 0x00070003"},
            ]
         },
         "launchCompleteCommand": "exec-continue"
      }
   ]
}

And here is a piece of the log where VSCode instructs gdb to set breakpoint on main():

1: (1022) <-1014-break-insert main
1: (1034) ->1014^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x08014f34",func="main",file="Main.c",fullname="d:\\Oleg\\!Projects\\HAMHard\\TrcrvNew-(Neon)\\Soft\\Ctrl2\\Ctrl\\Main.c",line="1317",thread-groups=["i1"],times="0",original-location="main"}
1: (1034) ->(gdb)
1: (1034) 1014: elapsed time 12
1: (1034) ->&"\n"
1: (1034) ->^done
1: (1034) ->(gdb)

Please tell me if you need the full log, or other information...

BTW, Several months ago it worked fine.

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.