question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

config files .cortex-debug.json in wrong folder of workspace

See original GitHub issue

My project is using a workspace with several directorys. To get the git extension showing all included subdirs with git, I add the main workspace as last entry in the workspace file. The cortex-debug extension creates .cortex-debug.peripherals.state.json and .cortex-debug.registers.state.json. But not in my main workspace, they are put in the first folder in the workspace.

this is part of my .workspace.code-workspace:

{
	"folders": [
		{
			"path": "lvgl"
		},
		{
			"path": "mbed-os"
		},
		{
			"path": "lvglDriver"
		},
		{
			"path": "custom_targets"
		},
		{
			"path": "."
		}
	],

The cortex config is now created in lvgl/.vscode, which is not wanted because it changes the git repo. cortex-debug has

"cwd": "${workspaceRoot}",

so it should use this for storing the configuration. How can I fix it?

it looks like it is created here: https://github.com/Marus/cortex-debug/blob/2bd83e0366beac890308bdeb664f83f3dcc7a701/src/frontend/views/peripheral.ts#L164

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8

github_iconTop GitHub Comments

1reaction
haneefdmcommented, Oct 8, 2021

Could you try out the latest (pre-release)

https://github.com/Marus/cortex-debug/releases

I have not implemented what I wanted as it is a bit more involved and takes time for testing.

Please close this if you find it working

0reactions
JojoS62commented, Oct 13, 2021

ok, sorry, it looks like the cmake extension is writing now this stuff. I’m using some manual configuration, its annoying because I have turned off all automatic that I could find already. Content of the file was {“DebugSessionRunning”:false}

So not a debug-cortex problem now.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Problem understanding cortex-debug configurations in Visual ...
Hardwarewise I'm using a STM32L433 Nucleo-Board with the build in ST-Link debugger probe. I created my project in VSC and created a launch.json...
Read more >
Cortex-Debug for Visual Studio Code | Alone on a Mountaintop
Here is a list of parameters in launch.json . Configure them for your specific device and environment. "cwd" : Path of project; "configFiles"...
Read more >
March 2022 (version 1.66) - Visual Studio Code
VS Code for the Web - Drag and drop files and folders into vscode.dev. ... Previously, users had to open the workspace settings...
Read more >
Debugging in Visual Studio Code w/ GDB + Cortex-Debug ...
Create a launch.json file (there should be a prompt in a few ... such as ${workspaceRoot} to get the absolute path to the...
Read more >
Feed Detail - STMicroelectronics
Regarding Cortex-Debug extension, all tools must be already in your (Windows) Path variable (arm debugger executable and openocd). Inside the main folder of ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found