Why can't I set a breakpoint in the eclipse?

Question

For some odd reason, I can't use breakpoints in my eclipse project. All the breakpoints that I set have a diagonal line on them, above the point in the corresponding line (in the left margin of the window), as if they were locked. When I start debug mode, breakpoints are ignored. Any ideas?

Answer 1

You probably clicked “Skip all breakpoints” in the breakpoint view. Just press again: D.

Default key bindings: Ctrl + Alt + B.

Answer 2

This doesn’t exactly answer the OPs question, but when I double-click to add breakpoints, I get the message that "this function is not enabled."

I needed to right-click on the line of the breakpoint and select "Types of breakpoints" → "Breakpoints C / C ++" instead of "Default". Then it worked fine.

Answer 3

• Open Debug View
• Open Breakpoint Perspective
• Right click all breakpoints there
• Click Enable

Answer 4

in python, I had to go to: windows-> perspective-> Open Perspective-> Debug then select the Breakpoints tab and make sure that zero with a slash (skip all breakpoints) is not selected (you can also use Ctrl-Alt -B to switch).

Answer 5

My "switch point" and other menu options were disabled. I restarted Eclipse (Kepler SR1) and they returned. I could set breakpoints again!

Answer 6

In my case, I edited my code during debugging, adding a zero check so that I could place a breakpoint to stop execution only when a certain value was zero. I could not add a breakpoint because the line of code in question was not present in the running application.

In Java, some code changes can be woven as soon as the file is saved, so in my case, remembering to save the changes was enough to place a breakpoint.

For changes that cannot be woven, the application must be restarted before new lines of code appear.

Answer 7

In my case, I opened the Breakpoints view, clicked “delete all breakpoints,” and then turned off the “skip all breakpoints” option, then turned it on. This allowed me to set breakpoints again. This was after restarting eclipse, which did not help.

Answer 8

I had a simulated problem, for me the standard code editor changed after installing a new plugin from the Marketplace. Apparently, the plugin decided to change the default editor for a large number of file types, and not just the one for which I installed it. The new editor did not allow setting breakpoints, but I did not know that it had changed at that time. When I right-clicked my source file in Project-explorer, I saw under the open list - with the new editor shown at the top. When I opened with the previous editor, everything became normal.