-exec-run Generated Process Name is Combination of GDB, CWD, and Program Paths #13252
Labels
Comments
|
Thank you for reporting this issue. We’ll let you know if we need more information to investigate it. Additionally, if you're working with GDB/LLDB, please note that the code is open source at https://github.com/microsoft/MIEngine/wiki/Contributing-Code . Your contributions are always welcome and appreciated. |
github-actions
bot
added
the
help wanted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Bug Summary and Steps to Reproduce
Bug Summary:
I am trying to debug a Ceedling unit test.
Using the "Ceedling test" task, I run the test and it compiles successfully and runs the unit tests. When I try to debug the program through the program the "(gdb) Launch" through the "Run and Debug" sidebar, I get the error below and the debug process is halted immediately.
ERROR: Unable to start debugging. Unexpected GDB output from command "-exec-run". Error creating process /usr/bin/c:/Checked_Out/Memory_Seat_Module/Memory_Seat_Module_FW/c:/Checked_Out/Memory_Seat_Module/Memory_Seat_Module_FW/test_ceedling/build/test/out/test_bit_operations.out, (error 2: The system cannot find the file specified.))The path generated is incorrect. It is a combination of :
I've verified that the actual executable exists.
It does not matter if breakpoints are set.
Debugger Configurations
tasks.json { // See https://go.microsoft.com/fwlink/?LinkId=733558 // for the documentation about the tasks.json format "version": "2.0.0", "tasks": [ { "label": "echo", "type": "shell", "command": "echo ${workspaceFolder}" }, { "label": "Make", "type": "shell", "command": "./MakeProject.bat", "problemMatcher": [ "$eslint-compact" ], "options": { "cwd": "${workspaceFolder}" }, "presentation": { "echo": false, "reveal": "always", "focus": false, "panel": "shared" } }, { "label": "Ceedling test", "type": "shell", "command": "ceedling test:${fileBasenameNoExtension}", "problemMatcher": { "owner": "cpp", "fileLocation": [ "relative", "${workspaceFolder}/test_ceedling"], "pattern": { "regexp": "^(.*):(\\d+):(.*): \"(.*)\"$", "file": 1, "line": 2, "message": 4 } } "options": { "cwd": "${workspaceFolder}/test_ceedling" }, "presentation": { "echo": false, "reveal": "always", "focus": false, "panel": "shared" } }, { "label": "Ceedling coverage", "type": "shell", "command": "ceedling gcov:${fileBasenameNoExtension}", "problemMatcher": [ "$eslint-compact" ], "options": { "cwd": "${workspaceFolder}/test_ceedling" }, "presentation": { "echo": false, "reveal": "always", "focus": false, "panel": "shared" } } ] } launch.json { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "name": "(gdb) Launch", "type": "cppdbg", "request": "launch", "program": "${input:workspaceFolderForwardSlashes}/test_ceedling/build/test/out/${fileBasenameNoExtension}.out", "args": [], "stopAtEntry": false, "cwd": ".", "environment": [], "externalConsole": true, "logging": { "engineLogging": true, "trace": true, "traceResponse": true, }, "MIMode": "gdb", "miDebuggerPath": "c:/msys64/usr/bin/gdb.exe", "setupCommands": [ { "description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true }, { "description": "Set Disassembly Flavor to Intel", "text": "-gdb-set disassembly-flavor intel", "ignoreFailures": true } ] }, ], "inputs": [ { "id": "workspaceFolderForwardSlashes", "type": "command", "command": "extension.commandvariable.transform", "args": { "text": "${workspaceFolder}", "find": "\\\\", // Reason for four '\': https://stackoverflow.com/a/4025505/2909854 "replace": "/", "flags": "g" } } ] }Debugger Logs
Other Extensions
I've disabled all other extensions except cpptool and I still had the same problem. When I disabled all other extensions, including "command-variable", which is used to fix the slashes in my path, I had to hard code the path to the CWD and program in launch.json, but the problem remained.
Additional Information
No response
The text was updated successfully, but these errors were encountered: