Eclipse does not stop at breakpoints

Question

Eclipse 3.5.2 does not stop at breakpoints. It is as if the debugger is using an older version of the source file.

I tried the usual update, cleared all projects, built everything without changes.

It is already in debug mode and the breakpoint is checked.

* ok deleted the whole project and checked it again. but still curious what the problem is.

Answer 1

You may have clicked the Skip all breakpoints button in the Breakpoints view.

Answer 2

Thanks guys, it really saved my day. I supposedly clicked on the slippage points, if you did the same thing, this would cause a breakpoint to appear with a backslash character on them.

To return it to its normal state:

• Go into the debugging perspective.
• click on the breakpoint icon →> upper right corner of the screen, you can also go there through Window-> show view-> breakpoints.
• The fifth icon on the left you will see a break point with a backslash. click on it.

To confirm, try putting a breakpoint on any line, and it should look fine.

Answer 3

Press Ctrl + Alt + B

OR follow these steps

Answer 4

Sometimes you start debugging mode, but the debugger does not actually attach / disconnect. I also had this problem several times when my laptop responded very slowly. Rebooting always solved this for me.

Also try to do everything cleanly (works wonders in Eclipse).

Answer 5

Please do not check this in the Eclipse menu.

Run-> Skip all breakpoints.

I think this will be enabled all the time as soon as you select the "Delete all break points" option in the "Debug / Breaks" window.

Answer 6

It also happened to me, in my case it was due to the launch of GDB, and I had to go to the "Legacy Create Process Launcher". For this

• or change the default launchers to "Legacy Create Process Launcher", in Windows> "Settings"> "Run" / "Debug"> "Launch"> "Launchers by default".

• or select this trigger in the debug configuration of your application (Run> Debug Configurations> select the debug configuration). On the "Home" tab at the bottom, click "Choose another ...", select the "Use configuration settings" checkbox, and select "Legacy of creating a startup process."

Answer 7

Doing "Clean All" worked for me.

Go to the tab "Project" → "Clear" menu item.

In the Clear dialog box, select Clear All Projects. Leave the rest of the defaults. Click the OK button.

BINGO !!! Remote debugging began to work for me as beautifully as before.

Answer 8

I had a conditional breakpoint mistakenly entered at the method entry point. This breakpoint was deleted and it worked.

Note. Tried to Skip all breakpoints, clear all projects, upgrade, close Eclipse without any luck before nailing it.

Answer 9

Clearing all breakpoints fixed the problem (in the perspective of the debugger: Window → Remove All Breakpoints ).

Project recovery does not work for me.

Answer 10

I have all breakpoints turned on and configured as I should. But whenever I pressed "debug", it would only go through the program (press f5 / f6). Turns out the error was configured:

Right-click the project> debug configurations> Debugger tab> uncheck the "Stop at startup at:"

Answer 11

One of the reasons for this situation may be that you clicked “skip all breakpoints” when playback and other pictures are smaller than usual (because of the higher resolution screen). Another thing is that breakpoints stop only under VM threads, and not under normal threads!

Answer 12

I suddenly experienced skipping breakpoints as well as on the Eclipse Juno CDT. For me, the problem was that I set up optimization levels. As soon as I returned it, it worked fine. To set optimization levels, go to “Project Properties → C / C ++ Build → Settings → Pan Settings” depending on which compiler you use, go to → Optimization and set the optimization level: None (-O0). Hope this helps! Best

Answer 13

I had the same problem and I found the real reason.

I wrote some parallel / multi-threaded ones , while I added some breakpoints inside the code running in the new thread. So, when the JUnit tests have stepped over and stopped soon, the code will not reach and will not stop at breakpoints.

In this situation, we have to click and select " Save JUnit after checking when debugging " in the section " Debug Configurations ... "

Answer 14

switching the workspace worked for me. Go to File> Switch Workspace and select another folder (workspace) so that it and BINGO! Debugging began to work for me as beautifully as before.

Answer 15

go to the respiration point and click the 5th to eclipse-> window> → show view-> other → debug-> breakpoint and click on the 5th option (Skip all breakpoints)

Answer 16

Make sure you use the correct version of the JRE to debug your project. Especially if it is a third-party project.

Also make sure that no trigger point is set for any breakpoint.

Answer 17

1. Go to (eclipse-workspace)\.metadata\.plugins\org.eclipse.wst.server.core and delete all tmp folders.
2. Clean and restart the server.

Answer 18

Another solution worked for me. I also faced the same problem - the debug points were not updated, although they are displayed correctly in the IDE editor and on the Break Points tab.

My problem and solution: when creating a project, the "Default Output Folder" points to a different location. At a later stage, I skipped the project by selecting "Project Right Click - Configure - Convert to Maven Project". Thus, in my project file system there are two sets of output folders. Cleaning up the project several times did not help solve my problem. In the background, it was pointing to different binary files. Finally, when I uninstalled the Maven Feature and cleaned up the project, this time everything worked fine. Env: Eclipse Juno and JRE - J2SDK 1.5.

Answer 19

The breakpoints seemed to work and not work on the versions of Eclipse that I had been using for the last couple of years. I am currently using Juno and just experienced breakpoints not working again. The above solutions, although good ones, did not work in my case.

Here is what worked in my case:

• deleted project

• check it back from svn

• import it again in eclipse

• run "mvn eclipse: eclipse"

Since the project is also a Groovy / Http-bulder / junit-test project, I had to:

• convert a project from Java to Groovy

• add / src / test / groovy to the Java build path (source folders on the build path)

• enable "** / *. groovy" in the Java Build Path for / src / test / groovy

Answer 20

I get all breakpoints missed and flagged as warnings when using -O2 in compiler flags. Now it switches to -O0 -g in my makefile and breakpoints. Hope this helps.

Answer 21

If it does not stop even after SKIP ALL BREAKPOINTS , you can add this android.os.debug.waitfordebugger immediately before the breakpoint.

If you do this, your application will definitely wait for the debugger at this moment every time, even if you just run your application, which it will find only when your device is connected to the eclipse.

After debugging, you must delete this line to run the application correctly, otherwise the android will just wait for the debugger.

Answer 22

Try restarting eclipse, which sometimes works. I think there is some kind of cache.

Answer 23

In my case, the debugged code in JBoss was older than the code in the Eclipse project. Reconstruction .war solved the problem.

Answer 24

Single issue with Eclipse Luna. A clean project does not work. Perestroika did not work.

What makes it work is to remove the application on the device before each debugging.

Answer 25

I am using the Eclipse FileSync plugin for direct remote debugging. Make sure you check Allow different target folders and edit the Target folder file option in the tree view.

Setting the Default target folder with the Browse... button Browse... without Allow different target folders will set all the folders to the same target (I had both libs and classes installed by default for libs , so my breakpoints are not updating).

Answer 26

If the above comments did not help, you can keep in mind that some cmake / make projects require you to compile code with the debugging option enabled. Hooray, Paco

Answer 27

Starting with the June 2017 version of Eclipse 4.7 / Oxygen , a new concept called “Triggers for breakpoints” has appeared, which appears as a small “T” next to the “blue marked dot” breakpoint icon.

All other breakpoints that are initially suppressed by triggers will be hit only after any of the trigger points is pressed. All triggers are disabled after the trigger point has been reached and will be turned on again after switching on.

To reset all the "trigger" flags, you must perform the following steps:

1. Switch to the debugging perspective.
2. Right-click in Breakpoints view
3. Select Delete All Triggers.

Note. This step does not delete all your control points, what happens when you select "Delete All" in the same context menu.

Note. The keyboard shortcut for triggers is Alt-R, which takes precedence on the shortcut to open the Run menu with its mnemonics when the Breakpoints view is selected.

Answer 28

My problem was that my debug window was closed, and when I tried to reach the breakpoint, the eclipse just hung and did not show where it stopped.

You can display Debug View on Mac by clicking Window> Show View> Debug

Answer 29

If cleaning up and rebooting the computer does not help, perhaps the reason is that the default debug port is used by another application. Changing to another value should work. In my case using IBM RAD:

1. Open the administration console
2. Go to Server / Server Types / WebSphere Application Servers. Click on the link [server1] (default name)
3. Open Java and Process Management / Process Definition
4. Open the Java Virtual Machine
5. On [Debug arguments] change the port number 7777 to a new one
6. Save and restart the Server. Done!

Answer 30

I had the same problem when I used Eclipse Juno. I installed Eclipse Indigo and it works great. Try reinstalling eclipse.