[rross]

Hello:

I have recently begun development on a brand new machine at my new job and debugging is not working - it just skips (almost) all my break points. Here's an example of what happens: When I launch my java swing app in debug mode and put in a few breakpoints (say one in the main method, one in a class constructor that I know is called, and a few others in one of the methods), it will stop at the main method breakpoint. I type F8 to resume and it stops at the constructor breakpoint. I type F8 to resume and it stops at the first breakpoint in the method. Now, the next time I type F8, it just runs and doesn't break. I have put prints between the last place that it breaks and the place that it doesn't, and also after the skipped breakpoint. The prints do print, but no break. (There are other scenarios where, if I sprinkle breakpoints, it won't stop at all.)

Some background:

Eclipse 3.5 (Galileo)
Java 6
Windows XP

I have used Eclipse for 7+ years and know the debugger, probably bet than I should. This is the first time this has happened to me and I am at a total loss. Other developers using the same code base do not have this problem. I have also tried using Eclipse 3.4, 3.3, 3.2. None of them work. I have tried a complete new install of Eclipse. Nope. I have tried different versions of java: java 5, jres and jdks. None of them work. I even zipped up one of my co-workers eclipse install and workspace and ran that. Nothing.

I thought that this could be an issue with the source and compiled code were out of sync, but I don't think that's the case. Could this be the OS? Has anyone out there seen this?

Any ideas would be greatly appreciated,
Richard.

[ggross]

I am having the exact same problem. I am running:

Eclipse 3.4
Java 6
Windows XP

Could this problem have anything to do with the project being a maven project?


Thanks,
Geoff

[rross]

I am not using maven. :-( I am at a total loss.

Richard.

[rross]

I am not using maven. :-( I am at a total loss.

Richard.

[_Oskar_]

I have a similar issue. My test seems to confirm that my project (that includes other projects also in the cvs) ignores breakpoints _after_ a call to a "other" project. The breakpoints before the "external call" works fine. I am using a two weeks old Gallileio release (Build id: 20090621-0832) on Ubuntu. However, these problems with Eclipse ignoring some breakpoints started a few weeks back, before I tried to solve it with updating my Eclipse. Back then, I was using a somewhat older Ganymede package.

I am not 100% sure what triggered the problems, but I believe a restart during my vacation due to powerfailure at work might be the culprit. Thats just a guess however.

My projects does not use swing, or apache. Its pure java / ant run from inside eclipse. Everything seems to work fine from code point of view. I have tried to clean / rebuild and conditional breakpoints and all sorts of things I could come up with, nothing helps.

[_Oskar_]

Hey, a collegue found the solution on a thread I had looked at, but not good enough apparently... ;p

Thread:
Eclipse: Java debugger is not stopping at breakpoints - Ubuntu Forums

Solution:
Window -> Preferences -> Java -> Installed JRE's -> (edit your currently used JRE) -> Edit "Default VM Arguments" box and enter (w/o questionmarks) "-XX:+UseParallelGC"

[ggross]

Originally Posted by _Oskar_

Hey, a collegue found the solution on a thread I had looked at, but not good enough apparently... ;p

Thread:
Eclipse: Java debugger is not stopping at breakpoints - Ubuntu Forums

Solution:
Window -> Preferences -> Java -> Installed JRE's -> (edit your currently used JRE) -> Edit "Default VM Arguments" box and enter (w/o questionmarks) "-XX:+UseParallelGC"

That worked for me, thank you so much.

I will let you know if I hear anything else that you may need to try.

[bbhomkar]

Hi,

Just try to use following values in the "Default VM arguments" instead of some default value

-Xms256m -Xmx512m -XX:MaxPermSize=128m

I think this will solve the problem.

[aruna.pahuja]

The solution specified above shall work for specific breakpoints but to be honest , the same problem occred for me as well and doign that didn't solved it.

You can try creating entry line breakpoints for the method you want to debug and then step to the required line.

Debugger in my system behave nicely at breakpoints created at method entry so its better to give it a whirl.