Open Klonan opened 3 years ago
Can you add the following to your launch.json
and share the output from the Debug Console
?
"logging": {
"engineLogging": true
}
Any further launch attempts result in nothing in the debug console:
This seems similar to:
I just ran the CodeLLDB debugger (which worked initially) then tried the C/C++ Extension debugger (which did not work) and then tried the CodeLLDB debugger again which then also stopped working.
From: https://github.com/microsoft/vscode/issues/130419#issuecomment-897011452
Where the first debug session succeeded, but subsequent ones are failing.
I noticed that with debug logging enabled, the recognized launch configuration is printed to the output panel of the C/C++ extension. This printed launch configuration contains the "noDebug": true flag even though the actual launch configuration doesn't contain it. "noDebug" is also true if explicitly set to false in the launch configuration. Does anyone know what causes this flag to be true? Could it have something to do with the executable in the program path?
Well, I don't know what changed, but now it does not even want to start at all.
I close VSCode, restart the PC, load it up, and when I press run and debug, nothing.
Nothing in debug console, nothing in any logs...
I tried doing a build task manually and it was stuck in Fetching build tasks...
I turned off the Detect tasks,
Now it works again
Bug type: Debugger
I run my program, it runs the program, I close the program. All fine.
However next time I try to run it, the launch does nothing, nothing happens. The 'Run and debug' panel shows the loading bar. The small panel showing 'Pause, Step Over, Restart, Stop' has only restart and stop enabled. Clicking these buttons will stop it, but trying to run again will not start it.
I have to completely restart VSCode to get ANY of my launch.jsons to work.
VS Code version: Code 1.58.2 (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:10:15.214Z) OS version: Windows_NT x64 10.0.19043 Restricted Mode: No
System Info
|Item|Value| |---|---| |CPUs|AMD Ryzen 7 3800X 8-Core Processor (16 x 4200)| |GPU Status|2d_canvas: enabledgpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|15.92GB (7.08GB free)| |Process Argv|--crash-reporter-id 42ffcc9f-d1e9-4d04-96a9-4708692910f8| |Screen Reader|no| |VM|0%|
Extensions (4)
Extension|Author (truncated)|Version ---|---|--- factoriomod-debug|jus|1.1.11 cpptools|ms-|1.5.1 fastbuild|Ros|1.0.0 vscode-autohotkey|sle|0.2.2A/B Experiments
``` vsliv368cf:30146710 vsreu685:30147344 python383cf:30185419 pythonvspyt602:30300191 vspor879:30202332 vspor708:30202333 vspor363:30204092 vstes627:30244334 pythonvspyt639:30300192 pythontb:30283811 pythonvspyt551cf:30345471 pythonptprofiler:30281270 vsdfh931:30280409 vshan820:30294714 vstes263:30335439 vscorecescf:30322572 pythondataviewer:30285071 pythonvsuse255:30340121 vscod805cf:30301675 pythonvspyt200:30340761 vscextlangct:30333562 binariesv615:30325510 vsccppwt:30329788 pythonvssor306:30344512 bridge0708:30335490 vstre464:30346472 ```One of the launch.jsons, they are all similar, just calling different fastbuild tasks:
Launch json
``` { "name": "Factorio Test Debug", "type": "cppvsdbg", "request": "launch", "program": "${workspaceFolder}/bin/Debugx64vs2017/factorio-test.exe", "args": [ //"--test", "TrainGroup" //"--suite", "Train" // //"--suite", "InputAction", "--fork", "-w" //"-i" ], "stopAtEntry": false, "cwd": "${workspaceFolder}", "environment": [], "console": "newExternalWindow", "preLaunchTask": "FastBuildTestsDebug" } ```https://user-images.githubusercontent.com/11986037/128830777-51698dd2-317f-41a8-aff8-273adef767bc.mp4