A couple of GoLand versions ago, the GoLand debugger stopped stepping into functions properly.
It works partially but with annoying caveats.
The debugger is stopping on breakpoints and step-over is working fine, but when I step into a function:
the debugger jumps to the definition of the function (as it should)
then when I press either step into/over, debugger just behaves as if I presses the continue button (F9) button and stops debugging.
I tried specifying a custom delve installation and it did not help. This happens on all types for code from hello world to unit test to gRPC service. Using GUI keys instead of keyboard shortcuts made no difference.
Anyone have an idea?
EDIT:
GoLand version 2022.3.2, Go 1.17/1.18 running on MacOS 13.2.
Related
I worked on a Console Application with a friend today. Is it possible to share the default console during a Live Share session? What I mean is that we had to compile and run our program manually through the default Windows Terminal to see output(which wasn't the best idea, there was a ton of empty lines displayed every time we would input anything), and debugging was impossible because we just couldn't see the console (only the host could).
According to the docs, it's possible to share the terminal in both VS Code and Visual Studio, but I don't think there's a way to share the console that comes up when you debug a console app. The solution I see is simply sharing a terminal, running your app in it manually and if you want debugging, you can try attaching the VS debugger to the console app's process after you start it manually by following this guide.
Recently my Visual Studio started to experience a delay before the program Starts Without Debugging.
This happens only when the following are met:
Console application
Start Without Debugging
There has been any change in the editor window from the last time program run.
After pressing Ctrl+F5 console application window opens and the cursor is active, but the execution is delayed.
The delay seems to be consistent in length (7-10 seconds), and not depend on the size of the code. I have checked two different installations of VS (2013 and 2015) on the same computer and the problem persists.
I have also checked that this delay occurs even for an empty Main().
There is a possibility that I have enabled some kind of an option/function in VS that causes this very specific delay, but I am not sure when this issue started occurring so I cannot trace back the change.
What could be the reason for this delay?
I will be grateful for help in this matter.
I made many attempts to diagnose the issue of the delay and one of the times that I pressed ctrl + F5 I have spotted a window opening in the background.
(It was definitely not visible everytime i tried to run without debugging).
It turns out that a functionality of Avira anti-virus had been scanning the code before it run for the first time. That is why when I made no changes to the code there was no delay.
Avira "Protection Cloud" is the name of the functionality responsible for the delays.
Link to Avira page about it and how to disable it: https://www.avira.com/en/support-for-home-knowledgebase-detail/kbid/1514
Sometimes if I have multiple editting windows open, this slows starting and stopping the debugger. Close all but those you are interested in and try again.
In a React Native project, I have some breakpoints (in Google Chrome DevTools).
I then decide to deactivate them and switch the "Activate Breakpoints" button to "blue" color:
...which works (no breakpoints are triggered while I continue running the application).
However, when I reload the application the breakpoints do trigger despite the "non-activated" flag exists:
This should not be happening.
The only way to ignore the breakpoints is:
- Activate them again
- Press F8 to continue
- Deactivate them
(then, the application continues running without breakpoints).
Is this a known bug? Do you also experience it and if yes is there any solution to this?
Thank you!
RN developer tools are still in testing phase. For MAC they are more stable than comparing to windows. The reason is actually the bundling of assests and js files.
the console takes it as a single file and then distributes it to different files that are showing in the workingdebugger.js file.
So it recreates them every time you reload the app.
Does anyone ever use vs just-in-time debugger on Firefox plugin-container.exe?
I want to debug my Firefox plugin on start-up, so I try the just-in-time debugger on plugin-container.exe. I expect once the plugin-container.exe is running, it will trigger the debugger, when I can start VS to debug it.
However, I met the following error, and it happens on each plugin I try to load.
What is wrong here? I am using Firefox 23.0.1
You can't launch the plugin-container.exe with the JIT debugger; what you can do is connect to it after it launches. The easiest way to do this is to add a Sleep(10000) in the NP_Initialize or DllMain functions so that you have time to connect the debugger to the process.
As Georg suggested, the tips page he linked to has some other ideas you could use.
Visual Studio 2005 C++
Windows XP Pro
I have a sample application that I am testing, that links with boost libraries.
However, the program runs ok. However, when I try and stop the program by clicking the 'Stop Debugging' button. The program ends, but the console window remains open. So I have many of them, as during my testing I am starting and stopping the application.
Even when I try and close it by clicking the close button it has no affect. And it doesn't seem to appear under task manager when the program ends.
The only way I can close them if I reboot windows.
I am thinking it might be a thread that has not closed, and maybe that is keeping the console windows open.
Many thanks for any advice,
I have also seen this issue, I think it happens when a mutex or semaphore is still locked, or a thread hasn't cleanly exited. The only way I've found to prevent this is to make sure all mutexes/ semaphores/threads are cleaned up after before stopping the debugger.
Also it's interesting to note that this problem doesn't happen on Windows 7 or Linux. I have tried stopping the same program at the same places and the program always cleanly exits.
Good luck and happy coding!