Closed zminic closed 4 months ago
If you use Go to definition
feature, does it open the problem file in VS Code? The debugger is reusing the same class file resolving function as the Red Hat Java extension.
"Go to definition" stops working for the entire project at some point if this package is included. It works when I open vscode, but after some time (I think when compilation is done) it stops working and output for java language extension shows similar error as the one above.
this duplicates with https://github.com/redhat-developer/vscode-java/issues/3139
Debugger stops on the breakpoint (as seen in callstack), but there is no change in the rest of the editor and I can't step through the code.
Environment
Steps To Reproduce
Current Result
When debugging is started in Call Stack window I can see that thread is paused for breakpoint, but there is no visual cue that we are in debug mode and can't proceed debugging.
Call stack window shows error message: "Malformed input or input contains unmappable characters."
Expected Result
I'm able to step through the code.
Additional Informations
When cucumber-java package is removed debugging starts working again.