-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GDB debugging session never starts #99
Comments
No this should not be required. Can you share your setup so that we can try to reproduce the problem. |
try externalConsole=false in launch.json |
Same problem here. @wolfired's suggestion works for me perfectly! |
//fyi @weinand |
The C++ extension (cpptools) needs to improve its error handling/reporting. See microsoft/vscode#67296. |
OK, the |
@rkeithhill since "attach" does not launch the target but just "attaches" to it, I don't understand how an "external terminal" can be involved here? |
Same problem here but @wolfired's trick does not work for me. Version: 1.35.0-insider (user setup) |
I just meant that there isn't a workaround like that for the |
@rkeithhill in the "attach" case the user is responsible for launching the debug target. So he can freely choose what terminal to use (and VS Code does not open a terminal automatically). So I do not understand why a workaround would be necessary at all. |
It's not about the terminal. It's about the fact that I haven't been able to attach to a process using I start the attach session, I enter the pid for the pwsh process and then I get this error in the "cppdbg: pwsh" terminal window: |
@pieandcakes when "attaching" gdb to an already running process (an "attach" instead of a "launch" debug config), do you run gdb via DAP's If yes, this would have the same problem as the "launch" case: if no external terminal is available or properly configured, the attach will fail. Would it be possible to run gdb without a terminal, e.g. by forking gdb as a process and talking to it via stdin/stdout? |
@weinand we support the |
@pieandcakes could you please take over this issue for investigation? |
@rkeithhill A workaround for getting attach to work in WSL to run @weinand This scenario is where we know ptrace_scope is not set or non-zero, so we send the following prompt: |
Issue Type: Bug
Expected:
Debug session starts up, connects to gdb server and my breakpoint is hit.
Actual:
Debug session just spins and never starts.
I'm using:
Do I need to be on the insiders version of the MS C++ extension?
Extension version: 0.32.0
VS Code version: Code - Insiders 1.34.0-insider (473af338e1bd9ad4d9853933da1cd9d5d9e07dc9, 2019-05-01T00:22:05.899Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 4.4.0-17763-Microsoft
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: