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
Related
For almost every page I open in Firefox, I see this error in the Console of the developer tool bar:
(!) The Components object is deprecated. It will soon be removed.
The source is the html page. It happens with pages I create, but also on many common websites.
I found this documentation on Components object on MDN web docs, but that does not clarify a lot. Note that even that page shows this message(!)
It looks like a warning, but according to the Console filter, it is an error.
My main questions are:
Is this something for me, as a developer of the page reporting this, to solve?
If so, how do I go about that?
I am not aware of any problems as a result of this. For now, that is.
I have seen this for over a year, maybe longer. I mostly ignore this, but every now and then it starts nagging me again. I don't want my code to break suddenly and would like to get rid of this message obscuring other messages.
This is not for the developer of the page to solve.
While biking back home, a possible cause popped up in my mind: could one of the add-ons I use cause this and yes, that appears to be the case.
I restarted with disabled add-ons and the message was gone.
Then I enabled them one at a time and the culprit is
Selenium IDE.
A bug report on this issue was closed with Won't fix, with the message:
This error will resolve itself when we move to a native app later this year.
In a MozillaZine topic of 2012, it is explained how it could have been solved.
The first one is just a warning that the addon is using "Components"
directly, which won't necessarily always be possible when using the
Add-on SDK. (The preferred way to do it is to access the aliases for
Components.classes and Components.interfaces and such that the SDK
provides by requiring the "chrome" module.) It shouldn't be a problem
right now, but might become one in the future.
it happened for me after installing Selenium plugin in my FireFox.
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.
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?
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...
I'm using IntelliJ Idea 8.1.2 for Grails development. The dynamic nature of Groovy is giving me a hard time debugging my code: I keep ending up in the internals of Groovy/Grails, i.e. CachedMethod, ExpandoMetaClass or the like.
Is there a way for example to tell the Idea debugger to completely skip the Groovy/Grails internals while debugging and only make steps in my own code? I did notice that there is a configuration option named "Do not step into specific Groovy classes" in Debugger > Groovy but so far I've noticed no difference.
If not, what is your workaround or how do you cope with the situation? Any help would be greatly appreciated.
File->Settings->Debugger->Stepping
Do not step into the classes...
Yeah, I suffer with this annoyance, too, and I don't have a good solution. My workaround once I'm lost in Groovy/Grails code is just to figure out where I should be back in my code, set a break point there, and hit Continue.