RahulSisondia
commented
4 years ago I think the problem mentioned at https://github.com/microsoft/vscode-cpptools/issues/3829 has resurfaced. I am also facing the same issue.
Closed ashishbinu closed 4 years ago
RahulSisondia
commented
4 years ago I think the problem mentioned at https://github.com/microsoft/vscode-cpptools/issues/3829 has resurfaced. I am also facing the same issue.
ashishbinu
commented
4 years ago I also tried downgrading the cpp tools to version 0.27.0 . Still the same problem exists.
WardenGnaw
commented
4 years ago @ashishbinu Could you provide more information on "C/C++ debugger is not working"? Can you not hit breakpoints, or can you not step through code?
@RahulSisondia #3829 is for lldb. This issue is using gdb. Can you open another issue with the problems you are encountering?
ashishbinu
commented
4 years ago @ashishbinu Could you provide more information on "C/C++ debugger is not working"? Can you not hit breakpoints, or can you not step through code?
No , it was not even running the code and debugger was not able to hit any breakpoints.
WardenGnaw
commented
4 years ago It looks like the debug sesion has started, it has stopped at main and the program is currently running.
The breakpoint fails to bind because it could not find the information it needs: Module containing this breakpoint has not yet loaded or the breakpoint address could not be obtained.
From:
--> R (setBreakpoints-4): {"type":"response","request_seq":4,"success":true,"command":"setBreakpoints","body":{"breakpoints":[{"id":1,"verified":true,"line":58}]},"seq":172}
--> E (breakpoint): {"type":"event","event":"breakpoint","body":{"reason":"changed","breakpoint":{"id":1,"verified":false,"message":"Module containing this breakpoint has not yet loaded or the breakpoint address could not be obtained.","line":58}},"seq":174}How are you building your program?
ashishbinu
commented
4 years ago How are you building your program?
I first compiled the c code with gcc and then hit F5 for debugging the code.
WardenGnaw
commented
4 years ago Can you share your tasks.json or the command line you use to compile the code?
ashishbinu
commented
4 years ago Can you share your
tasks.jsonor the command line you use to compile the code?
I am not using task.json . I used gcc to compile my code in konsole(terminal emulator) .The program is also going into the main code as it prints the Hello in terminal but after typing 3 as input to scanf() it seems to not respond.I have put two images of my terminal and debug console below :
Darky-Lucera
commented
4 years ago The C/C++ debugger (GDB) also stopped working for me on Windows 10, MacOS (Mojave) and Linux (Ubuntu 18). I don't know exactly when because lately I have been working with python (some months) instead of C++ and when I have came back it has stopped working after update VSCode and the C++ plugin and CMake plugins.
Curiously, if I put a breakpoint and I press Debug or F5 it works but if I remove it and put it again it turns gray and don't work anymore.
This is my debug console log:
=thread-group-added,id="i1" GNU gdb (GDB) 8.3.1 Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-w64-mingw32". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/.
For help, type "help". Type "apropos word" to search for commands related to "word". Warning: Debuggee TargetArchitecture not detected, assuming x86_64. =cmd-param-changed,param="pagination",value="off" [New Thread 14052.0x1e20] [New Thread 14052.0x2450] [New Thread 14052.0x354]
Thread 1 hit Breakpoint 1, main () at C:/Work/minifb_emoon/tests/noise.c:24 24 uint32_t i, noise, carry, seed = 0xbeef;
Thread 1 hit Breakpoint 2, main () at C:/Work/minifb_emoon/tests/noise.c:47 47 state = mfb_update_ex(window, g_buffer, g_width, g_height); Execute debugger commands using "-exec
", for example "-exec info registers" will list registers in use (when GDB is the debugger) [Thread 14052.0x1e20 exited with code 0] [Thread 14052.0x2ed8 exited with code 0] [Thread 14052.0x354 exited with code 0] [Inferior 1 (process 14052) exited normally] The program 'C:\Work\minifb_emoon\build\noise.exe' has exited with code 0 (0x00000000).
BTW, I don't put the Breakpoint 1
This is my 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": "${fileDirname}\${fileBasenameNoExtension}.exe", "program": "${command:cmake.launchTargetPath}", "args": [], "stopAtEntry": false, "cwd": "${workspaceFolder}", "environment": [], "externalConsole": false, "MIMode": "gdb", "miDebuggerPath": "C:\MinGW\bin\gdb.exe", "setupCommands": [ { "description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true } ], //"preLaunchTask": "gcc.exe build active file" } ] }
WardenGnaw
commented
4 years ago @ashishbinu You need to compile with debug symbols e.g. gcc -g file.c
ashishbinu
commented
4 years ago Thanks , @WardenGnaw now the debugger is working fine
gabrielbergoc
commented
2 years ago My debugger isn't hitting any breakpoints, and my file is being compiled with the -g flag.
tasks.json:
{
"tasks": [
{
"type": "cppbuild",
"label": "C/C++: g++.exe arquivo de build ativo",
"command": "C:\\MinGW\\bin\\g++.exe",
"args": [
"-fdiagnostics-color=always",
"-g",
"${file}",
"-o",
"${fileDirname}\\${fileBasenameNoExtension}.exe"
],
"options": {
"cwd": "${fileDirname}"
},
"problemMatcher": [
"$g++"
],
"group": {
"kind": "build",
"isDefault": true
},
"detail": "Tarefa gerada pelo Depurador."
}
],
"version": "2.0.0"
}launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "g++.exe - Criar e depurar o arquivo ativo",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}\\${fileBasenameNoExtension}.exe",
"args": [],
"stopAtEntry": false,
"cwd": "C:/MinGW/bin",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "C:\\MinGW\\bin\\gdb.exe",
"setupCommands": [
{
"description": "Habilitar a reformatação automática para gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
},
{
"description": "Definir Tipo de Desmontagem como Intel",
"text": "-gdb-set disassembly-flavor intel",
"ignoreFailures": true
}
],
"preLaunchTask": "C/C++: g++.exe arquivo de build ativo"
}
]
}The build is finished successfully, and then this is executed in the integrated terminal:
but I can't type anything.
I would really appreciate any help on this, It's so frustrating being unable to properly debug my C++ programs...
Type: Debugger
Describe the bug
My launch.json configuration : ` {
} `
Additional context
launch.json: *