Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Eclipse stops at non-existent breakpoint

I have an Eclipse (java) project which stops at non-existent breakpoints. There was a breakpoint at this location at one time, but I removed it. Any ideas why this would be happening?

Note: It is not the same issue mentioned here - phantom breakpoint driving me crazy!

like image 850
Geoff Avatar asked Aug 24 '11 15:08

Geoff


People also ask

Why breakpoints are not working in Eclipse?

The debugger stops at main because a temporary breakpoint was set there. You don't see it because it evaporates as soon as it is hit. So, Eclipse IS setting breakpoints that work.

How do I fix Java exception breakpoint in Eclipse?

You can fix this immediately by opening the Markers view and delete the Java Exception Breakpoints. However, to permanently remove this type of breakpoints, you have to go to the Java Debug options and uncheck the "Suspend excecution on uncaught exceptions" option.

How do I use toggle breakpoint in Eclipse?

Breakpoints To define a breakpoint in your source code, right-click in the left margin in the Java editor and select Toggle Breakpoint. Alternatively, you can double-click on this position. The Breakpoints view allows you to delete and deactivate Breakpoints and modify their properties.

How do I debug an entire project in Eclipse?

Starting the Debugger. To debug your application, select a Java file with a main method. Right-click on it and select Debug As Java Application. If you started an application once via the context menu, you can use the created launch configuration again via the Debug button in the Eclipse toolbar.


2 Answers

I have suffered this. To fix it, just goto Run->Remove All Breakpoints in the menu. It will remove it. Later you can redefine your required breakpoints again.

like image 113
Suraj Chandran Avatar answered Oct 19 '22 16:10

Suraj Chandran


If you are sure that there aren't breakpoints (Run > Remove All Breakpoints), then there are 2 things to consider:

  1. You are misunderstanding something of how the debugger works.
  2. Your program is stopped because it's waiting for some input.
like image 43
Heisenbug Avatar answered Oct 19 '22 15:10

Heisenbug