![]() That is, we build "Source/Application/main.c" to "build/Source/Application/main.o". When we build object files, they are built to a build/ folder with the same relative path from the project root. "Source/Application/main.c" is the workspace relative path of the file and I confirmed that this is the path that is provided to gcc. ![]() I only have one elf in my tree so I don't think I'm looking at two different files. and set a breakpoint at the spawnSync, single step - I would have liked to put this code in there permanently except for the console.log in symbol.ts right after the spawnSync call. You can set breakpoints in either front end or backend or both and stop at appropriate points. They are running in separate programs (node instances) and they communicate via the port 4711. You will now be able to run debug both the backend and the extension frontend. Open your embedded program, edit launch.json, add the following line. This will open another instance of VSCode with the Cortex-Debug extension. In Debug panel, use the 'Extension + Debug Server' launch configuration. I am assuming you know how to compile and watch for changes in your source code. Start by closing all other VSCode top level windows and just have the extension folder open. I am not sure how you are currently debugging the extension? You can use VSCode to debug the extension.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |