While this question has been asked repeatedly, the current answers just are not working for me.

Things tried thus far:

-- starting in Debug perspective
-- upgrading version of Eclipse
-- trying to clean out Eclipse.ini (cannot find a version of eclipse.ini)
-- checking for "skip all breakpoints" being checked (it is not checked)
-- Run > Debug Configurations, that 'Stop in main' is selected

1 Answer
1

One more thing to look at is if you are setting the breakpoint on the right thing.

If you are using dependency management (e.g. Maven), then it is not unheard of for you to get two different versions of the same class brought in from two different places. Then you might open a resource, set a breakpoint on it, but run the other version.

Another possibility is for something like Maven to put the JAR of a checked-out project on the classpath, leading to you setting a breakpoint on the class that is in the output folder, but running the one from the JAR.

If you are using a servers view (e.g. running in Tomcat), similar things can happen due to the deployment assembly (in the project properties).

There are many ways you can end up with this problem, but most of them boil down to not setting the breakpoint on the thing you are actually running.

Good point. I pasted in my code above. It is incredibly simple and I'm not using anything like Maven or GUICE. It is one simple file, which is why I am so stumped.
–
eb80Dec 20 '13 at 4:21

Clarification: You mention you are using the debug configuration's "stop in main"...have you tried clicking on the line number in the editor margin to set the breakpoint explicitly? Also, make sure you are doing "Debug as..." and NOT "Run as...".
–
Tony K.Dec 20 '13 at 4:35