I was debugging a GoLang program. I set break points and run the debugger. But the break points only works the first time I run the debugger and failed in the second, the third, and all following debugging whatever I do. I cancelled them and reset them, I close the debugging window and open a new one, I change the settings in the "Breakpoints" tool window. All these didn't work at all.
What's the problem?
Update, this has been fixed in the latest release of the plugin, please check it out
This is a well known problem and it lies in delve not the plugin itself. Please see this this issue for further reference.
Related
I have a single project in VSCode where breakpoints are not working and I can't figure out why. I'm new to VSCode but I've got them to work in other projects (Pascal) but there's something about this one it doesn't like.
Does anyone at least know what this means when the break points are gray like this? Is it a bug? In the 2nd screenshot you can see I can run LLDB from the terminal on the same executable so it's not LLDB messing up.
This might be an obvious answer, but it's what solved the issue for me when I encountered it.
Recompile the program and try again
I have an R script that doesn't throw what I expect it to. However, it does run all the way through. To fix it, I've tried setting a breakpoint in order to enter debug mode.
But when I do this, I get an error that says:
debugSource('~/mycode/konfio/Projects/Interest Rates/src/getPARS.R', echo=TRUE)
Error in if (length(funBody[[idx]]) != length(originalFunBody[[idx]]) || :
missing value where TRUE/FALSE needed
I've Googled this error, but only found one link which didn't help. If anyone knows how to get my hands on the Debugger, or somewhere else that I can search for the problem I'll be grateful.
Thank you.
RStudio's breakpoints work by rewriting your function to include debug code. The most likely cause of this problem is a bug in RStudio that's causing it to fail to rewrite your function. There are a few possible solutions:
Remove just the statements you want to debug and put them into a separate function. Set the breakpoint on that function and call it from your main script.
Use browser() based-debugging: just add browser() where you would have set a breakpoint (RStudio's debugger works with R debugging features, too).
Use a newer version of RStudio. Debugging R scripts (as opposed to functions) has improved a lot lately, and if you're feeling especially brave you can try a daily build.
If you have time, please post the contents of the file you're having trouble with to RStudio's support forum; we'd like to take a look and see if we can make a fix in an upcoming version.
I recently installed the JRebel plugin for NetBeans and have noticed the following problem when debugging within the IDE:
If I set a breakpoint in a class and change the code afterwards, then my debugger doesn't always hit the breakpoint. I found a workaround: resetting the breakpoint (or reattaching the debugger to project) after reloading the class.
But this solution is not perfect because class is reloaded when app needs it for the first time(debugger doesn't work yet) so I have to make some action which I want to debug two times which can cause so many problems.
Another thing is what I can't explain at all.. even when I hit the breakpoint with success, I can't hit another one in another class.
Maybe someone has figured this issue out - ? Is there a way to reload changed classes on save?
NetBeans 7.2.1 with JRebel plugin, Glassfish 3.1.2
This is a known issue. The solution exists but not released yet.
Also, please check Options->Java->Java Debugger. Is the "Apply code changes after save" checkbox enabled? If not, could you enable it and try in this configuration - will it make any difference?
I wanted to know is there any way in IDEA putting debuggers' breakpoint to previous row where debugger has just passed and re-run that scenario again. Because when debugging a loop, it's a bit tedious going to a UI doing desired action for handling that case again. I think such feature is available in Visual Studio. I've tried to google it but unfortunately I could not found anything about it.
I've submitted an issue on IDEA's bug tracker but its status changed to won't fix with this comment:
This functionality is not supported by the JVM. It's not possible to
implement it in IntelliJ IDEA without JVM support.
http://youtrack.jetbrains.com/issue/IDEA-84257?projectKey=IDEA
MyProject has triggered breakpoint
without any brakepoints in my project (i have made sure using Debug/Delete all BP)
I do not really post some code, because project is really big and it is also impossible to make some minimal sample.
Where sould I look when getting this error?
TY
I had a similar problem recently, where it was stopping on a breakpoint that no longer existed, and my Code Coverage highlighting was reflecting an older run, somehow. Not sure why, but things were out of sync between what was current state and what it was previously. For my instance, I was able to do a Clean Solution, then shutdown and restart VS 2010 and the problem went away.
Has only happened to me the one time, so I am not sure what I could have done to cause it. Didn't see anything similar logged on Connect, either.
Your debugger might be set to break when an exception is thrown.
Go to Debug -> Exceptions... -> make sure all the boxes are unchecked.
Without any more info I can't help...