02 June 2009

Breakpoint problem with Eclipse 3.4 and JDK 1.6 update 14

I had problems that some break points did not take in my Eclipse 3.4.1 when I updated from JDK 1.6 update 12 to JDK 1.6. update 14. Well some breakpoints took, but none in the AWT thread. It could be a coincidence, I don't know.

I updated to Eclipse 3.4.2 but that did not solve the problem.

I had to downgrade to JDK 1.6 update 13 to solve the problem. It was enough to choose another JDK for my specific project. Eclipse itself could run update 14.

I searched the Internet but could not find any official bug either in Java or Eclipse. Anybody out there got more information?

Update: the problem is now fixed: http://blog.lesc.se/2009/09/jdk-breakpoint-problem-fixed-in-update.html


  1. https://bugs.eclipse.org/bugs/show_bug.cgi?id=279137

    I experience the same problems. To me it seems that only breakpoints in anonymous inner classes don't get hit.

  2. I have same problem. Anyone reported this to Sun?

  3. I also have this problem as of today. Eclipse 3.4.0 and JDK 1.6 update 14.

    Breakpoints work in certain part of the code, but not in other parts. I even located two consecutive lines of code in the same class, where the breakpoint worked on the first line, but not on the second line.

    That particular method runs on the AWT-EventQueue thread.

    Very wierd.

  4. I tried the same fix as Lennart (downgrading to JDK 1.6 u13 for project, kept eclipse on 1.6 u14) and it worked for me as well, thx :)

  5. There is now an Eclipse bug report for this problem... however the bug report has been closed. It was the conclusion of the Eclipse teams that it appears to be a JRE/JDK bug; most probably in the GC code.