-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Breakpoints stoppped working #60747
Comments
Can yuo reproduce this with latest vscode insiders https://code.visualstudio.com/insiders/ |
I can reproduce this with VS Code Insiders. In my Go application, I set a break point and start the debugger using the following {
// 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": "API",
"type": "go",
"request": "launch",
"mode": "debug",
"remotePath": "",
"port": 2345,
"host": "127.0.0.1",
"program": "/Users/johnsonj/dev/omnivore/giganto/om/backend/api/cmd/api/main.go",
"env": {},
"args": [
"/Users/johnsonj/dev/omnivore/giganto/om/backend/api/config/config.ini",
"/Users/johnsonj/dev/omnivore/giganto/om/backend/api/config/dev_config.ini"
],
"showLog": true
}
]
} When execution hits a break point, the application is suspended but the UI is not right. You can see that the break point line is highlighted, but the step tools are in the wrong mode (as if no break point has been encountered and execution is not suspended. Unfortunately, I cannot share the application. Is there any environment information or logging that I can give you? |
@booleangate thanks for providing more details. I will keep this issue open so I am aware of it. |
👍 |
@booleangate yes please open an issue with vscode-go and they can start investigating. Thanks |
@ramya-rao-a are you also owning the go debug adapter? If yes did something change there and did you have users filling similar issues? |
@isidorn Yes, I own the Go debug adapter as well. @roblourens helps me there from time to time. |
@booleangate Please add Also, do you see similar issue in a simpler program that you can share? |
Switched back to August release 1.27.2, and works as it used to. @ramya-rao-a here is the trace from 1.28.1:
|
The issue for me is only when I'm trying to hit an http handler endpoint. Works well if I put a breakpoint in a main.go file(or any startup location). |
@ramya-rao-a Here's the debug log. Downgrading to 1.27.2 also fixes my problem. @jinmatt pointed out that he experiences the same thing in http endpoint handlers but not in main. I did a test and confirmed that I am experiencing the same problem with my application. Break points in main trigger as expected, but break points in http handlers exhibit the reported behavior. @jinmatt Are you able to share your application? |
@jinmatt yeah a reproducable case would be really useful here for us to investigate more. fyi @weinand |
I'm sick and barely functioning 😷 I'll try to whip something up when I'm on my feet again. |
Also try F1 > developer tools and opend debug console for potential errors |
An exception is being raised here https://github.com/Microsoft/vscode/blob/4f09f1aa4a47d0d9afc83dc601094b8e1f24c673/src/vs/base/common/uri.ts#L29
|
duplicate of #61088 |
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines. Happy Coding! |
Issue Type: Bug
As of 1.28.1, breakpoints in debugger suspend application, but debugger UI is not activated (cannot step debug).
VS Code version: Code 1.28.1 (3368db6, 2018-10-11T18:07:48.477Z)
OS version: Darwin x64 17.7.0
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: enabled
rasterization: unavailable_software
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Extensions (15)
The text was updated successfully, but these errors were encountered: