Eclipse doesn't stop at breakpoints

Question

Eclipse 3.5.2 is not stopping in breakpoints. It\'s as if the debugger is using an older version of the source file.

Tried the usual refresh, clean all projects, bui

Answer 1

A different solution worked for me. I also faced the same problem - debug points were not being updated, though they are shown correctly in the IDE editor and in Break Points tab.

My problem and solution are: While creating the project, the 'Default Output Folder' points to different location. At a later stage, I have mavenized the project, selecting "Project Right Click - Configure - Convert to Maven Project". So there are two sets of output folders exist in my project file system. Cleaning the project multiple times did not solve my problem. In the background it was pointing to different binary files. Finally, when I removed the Maven Feature and cleaned the project, this time everything worked fine. Env: Eclipse Juno and JRE is J2SDK 1.5.

Answer 2

I get all breakpoints skipped and marked as warnings when using -O2 in the compiler flags. Switched to -O0 -g in my makefile and breakpoints now work. Hope this helps.

Answer 3

I had the same problem, and I found the real cause.

I had written some concurrent / multi-threads code, while I added some breakpoints inside the code running in a new thread. So, when JUnit tests ran over, and stopped soon, the code will not reach and stop at the breakpoints.

For this situation, we have to click and select "Keep JUnit running after a test run when debugging" check box at "Debug Configurations..."

Answer 4

Make sure, that you are using the correct JRE version to debug your project. Especially if it's a third party project.

Also make sure, that there is no trigger point set for any breakpoint.

Answer 5

One reason for this situation can be, that you have pressed 'skip all breakpoints', when play- and another pictures are smaller than those normally are (because of higher resolution screen). Another thing can be, that break points are stopped only under VM threads, not under normal threads!

Answer 6

In my case the debugged code in JBoss was older than the code in the Eclipse project. Rebuilding the .war solved the problem.