Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve been using Eclipse for ages and I use the debugger all the time but recently I’ve known it to skip over breakpoints while debugging! I’ve even had it so that I’ve set a break point on a println I’ll see the text come out but not hit the breakpoint. Also sometimes I’ll hit a break point consistently in one area of the code but not in others. This never used to happen and I can’t work out what I’ve done to my system to cause this. Has anyone else had any experience of the problem?
What you mention (“
-XX:+UseParallelGC“) is a workaround for the bug found with jdk6u14 and 15.As mentionned in “Eclipse SWING app: breakpoint hit only after an uncaught exception is thrown”, it is fixed with jdk6u16.