-
Notifications
You must be signed in to change notification settings - Fork 1
Description
There is some inaccuracy in the documentation and a bug
I have a sample project zipped up that has been configured up as per the instructions in the README.md
This used to work with the old extension and ceedling 0.31.1
Unzip it to c:\Projects\VScodeDebug and load up the directory into VScode
It is expecting gcc.exe and gdb.exe to both be on the %PATH%
The tests run fine.
- Documentation error:
Then try and debug a test, by starting from the bug icon in the test panel:
[error] Debug error: Error: Configuration 'ceedling' is missing in 'launch.json'.
Go the launch.json and change the name of the configuration from "Ceedling Test Explorer Debug" to "ceedling"
- An actual bug?:
Try to debug a test again, by starting from the bug icon in the test panel:
[error] No debug test executable found
[info] A debug configuration with a path containing ${command:ceedlingExplorer.debugTestExecutable}
cannot be started from F5 or the Run pannel. It should be started from a bug icon in the Test pannel.
Then change
"program": "${workspaceFolder}/build/test/out/${command:ceedlingExplorer.debugTestExecutable}",
to
"program": "${workspaceFolder}/build/test/out/test_Unit1/test_Unit1.exe",
Try to debug a test again, by starting from the bug icon in the test panel.
It now allwos me to debug