Eclipse Debugging - Stopping without a breakpoint

Question

I am debugging some Java code with Eclipse 3.4.2. I have disabled all the breakpoints, yet the debugger still stops at a specific line. This point is several lines before a null pointer exception is triggered. Curiously, when I run the same code/run configuration, but not in the debugger, the null pointer exception does not occur.

Also, if I step through this code from the beginning of the method causing the null pointer exception, using the exact same input, there is no problem. It only occurs when I remove all breakpoints but Eclipse decides to stop there regardless.

Why could this be happening?

score 44 · Answer 1 · answered May 08 '11 at 10:05

44

I had the same problem and finally found the following configuration option: Windows -> Preferences -> Java -> Debug -> Suspend execution on uncaught exceptions I unchecked it, and the problem disappeared. However, may be it's good to know about uncaught exceptions. I just disabled it because the problem was in Spring framework, not in my code, and hence I could correct nothing... Hope it helps :)

answered May 08 '11 at 10:05

Mendo

441
4
2

Thanks for this answer - I was having the exact same problem but your answer has worked for me. – Paul Hollingsworth Jul 03 '12 at 13:10
after about 10 years this still works for me – fantaghirocco Oct 02 '22 at 07:42

score 18 · Answer 2 · answered Nov 03 '09 at 17:44

18

Eclipse also supports exception break points (which stop your program when a certain exception is thrown). You can see them in the "Breakpoints" panel of the debugger. In your case, this could be a ClassCastException, for example.

If that panel is empty, then it can be a bug in your Java VM or maybe you have two processes open in the debugger. If all else fails, try to debug it in Eclipse 3.5.1.

answered Nov 03 '09 at 17:44

Aaron Digulla

321,842
108
597
820

Thanks a lot! That was my case – Shpytyack Artem Sep 29 '17 at 10:51

score 4 · Answer 3 · answered Nov 03 '09 at 19:58

4

I've encountered this as well and have yet to find a satisfactory answer. Try doing a workspace refresh, full rebuild and restart Eclipse.

At least one of those suggestions will help.

Failing that - rebuild or restore your workspace (I always keep a backup)

answered Nov 03 '09 at 19:58

Fortyrunner

12,702
4
31
54

I deleted my workspace and it worked, hope it doesn't comeback – Ismail Marmoush Jan 28 '14 at 20:20
2

Also try Run->Remove All Breakpoints as per http://stackoverflow.com/questions/7178096/eclipse-stops-at-non-existent-breakpoint – KCD Mar 05 '15 at 03:06

Eclipse Debugging - Stopping without a breakpoint

3 Answers3

Linked

Related