Debugger not highlighting current line when breaking/stepping
Hi,
I have recently purchased IntelliJ 12.1.4 for a new development machine. I've been using IntelliJ for over 10 years now, at least, so I am an experienced user.
The issue I am having is with debugging Java code. If am using remote debugging to a local Tomcat server. In 10.5, the last version I used and every version previous that I can remember, when I hit a breakpoint in the IDE, a blue line would highlight which line the debugger had stopped at and then that highlight would move to the current line as I stepped through the debugger (F8). With 12.1.4, the debugger breaks but doesn't highlight the current line. F8 still works, I can see changes in the debugger window, but there is no blue line showing the currrent line, only the current line number in the debugger window.
Is this a known issue or some new setting in IntelliJ? It makes source-line debugging impossible.
Thanks.
Please sign in to leave a comment.
Hi there,
Maybe it's your color scheme? Can you please check that "Settings | Editor | Colors & Fonts | Debugger | Execution point" has proper background color assigned?
Any thoughts on this? This is a total dealbreaker. I cannot use IntelliJ for debugging Java.
Also, changing my theme to the dark one, I am not able to change it completely back. The editor window is the default but everything else remains the dark theme even though the settings say it's the default theme.
After 10+ years of using IntelliJ it's not like I can switch to something else. Can I use my 12.0 license to rollback to 11.x?
What do you mean exactly?
There are two places to change "colors":
On this note: there are Darcula GUI theme as well as Darcula editor theme -- you need to change them both (and restart IDE after changing GUI theme).
If you have changed both of them already but that did not helped -- see below.
I may only suggest trying clean install.
If no change -- you may restore all from backup. If it helped -- you may still restore most of your settings from backup if so desired.
Do you think a clean re-install will help the debugger issue?
IF (yes, big IF) problem is in actual IDE/project settings -- why not, especially since this will take like 5-10 mins max? (but for best results it needs to be tested on brand new project as well, unless you are happy to test this on real project, which means renaming/backup+delete project settings as well)
Ok, I will re-install. This was already a clean, brand new system and install so I am skeptical this will somehow fix the debugger not scrolling to or highlighting the current execution.
If this doesn't work I'll contact support and see if I can use my license to rollback to a previous version of IntelliJ. I have to get this working.
Re-installing and re-creating the project did nothing to change this.
When I debug Tomcat, it breaks but never shows the blue line at the execution point or does it jump the editor to the point of execution.
Double-clicking on any of the lines in the stack also doesn't jump to the point in the source.
There seem to be other posts here about debugging a remote Tomcat server now too so maybe there's a real issue?
For what it's worth, I installed IntelliJ 11.1.5, create a new project against the same source code and SDK with the same Tomcat server running and when it hits the breakpoint, it breaks and show the execution point with the blue line as expected.
For what it's worth, I installed IntelliJ 11.1.5, create a new project against the same source code and SDK with the same Tomcat server running and when it hits the breakpoint, it breaks and show the execution point with the blue line as expected.
So, at least I can work for 30 days until the trial expires unless my 12.1 license will activate it :)
I 99% certain that a license is valid for any and all previous versions. I am curious however why the issue is occurring in 12.1. I'd encourage you to keep trying to track down the issue as time allows since 12.1 brings some nice improvements to the table.
I had the same issue.
What fixed it was removing the "&" character from the folder which the file was located inside.
No idea why this causes this issue, but PyCharm does not like ampersands (&) in your package names.