Eclipse doesn t stop at breakpoints

Question

Eclipse 3 5 2 is not stopping in breakpoints  It s as if the debugger is using an older version of the source file   Tried the usual refresh  clean all projects  build all  with no change   Already in debug mode and the break point is checked     ok ended up deleting the whole project and checking it out again  but still curious what the issue was

User · Answer

I get all breakpoints skipped and marked as warnings when using -O2 in the compiler flags  Switched to -O0 -g in my makefile and breakpoints now work  Hope this helps

User · Answer

Press Ctrl   Alt   B  OR go through below steps

User · Answer

Sometimes you do start the debug mode but the debugger doesn t actually get attached gets detached  I ve also had this issue a few times when my laptop was reacting really slowly  A reboot always solved it for me   Also try doing a clean all  works miracles in Eclipse

User · Answer

I had all breakpoints enabled and configured as I should  But whenever I clicked  debug  it would only step through the program  press f5 f6  Turns out there was a rogue setting  Right Click project   debug configurations    Debugger  tab   uncheck  Stop on startup at   box

User · Answer

switching workspace worked for me  Go to File   Switch Workspace and choose different folder  workspace  That s it and BINGO  Debugging started working for me as beautiful as before

User · Answer

Running under Ubuntu 18 04LTS in a VirtualBox VM  This answer pertains to Eclipse PTP  By default  double clicking on the left margin was adding PTP Breakpoints  I am not familiar with PTP debugging   Those apparently do not make debugging stop  I right-clicked on a breakpoint - gt  Breakpoint Types - gt  C C   Breakpoints  and it started inserting this other  quot usual quot  type of breakpoints  You can tell one from the other  as they are indicated with large green vs  small purple circles

User · Answer

go breatpoint and click on 5th to eclipse- window - show view- other- debug- breakpoint and click on 5th option  Skip All Breakpoints

User · Answer

One reason for this situation can be  that you have pressed  skip all breakpoints   when play- and another pictures are smaller than those normally are  because of higher resolution screen   Another thing can be  that break points are stopped only under VM threads  not under normal threads

User · Answer

It has also happened to me  in my case it was due to the GDB launcher  which I needed to turn to  Legacy Create Process Launcher   To do so     either change the default launchers to the  Legacy Create Process Launcher   in Windows Preferences Run Debug Launching Default Launchers  or choose this launcher in the debug configuration of your application  Run Debug configurations choose your debug configuration   Under the  main  tab at the bottom  click on  Select other      check the box  Use configuration specific settings  and choose  Legacy Create Process Launcher

User · Answer

I had a conditional break point wrongly put on the method entry point  Removed that breakpoint and it worked   Note  Tried Skip all Breakpoints  Clean all projects  Refresh  close Eclipse with no luck before nailing it

User · Answer

Go to  eclipse-workspace   metadata  plugins org eclipse wst server core and delete all tmp folders  Clean and Restart server

User · Answer

Facing same problem with Eclipse Luna  Project clean didn t work  Rebuild didn t work   What makes it work is uninstall the app on the device before each debugging

User · Answer

Performing a  Clean All  worked for me   Click on  Project  tab --   Clean  menu-item   In the  Clean  dialogue-box select  Clean all projects  radio-button  Leave the remaining values as default  Click  OK  button   BINGO   The remote-debugging started working for me as beautiful as before

User · Answer

A different solution worked for me  I also faced the same problem - debug points were not being updated  though they are shown correctly in the IDE editor and in Break Points tab    My problem and solution are  While creating the project  the  Default Output Folder  points to different location  At a later stage  I have mavenized the project  selecting  Project Right Click - Configure - Convert to Maven Project   So there are two sets of output folders exist in my project file system  Cleaning the project multiple times did not solve my problem  In the background it was pointing to different binary files  Finally  when I removed the Maven Feature and cleaned the project  this time everything worked fine    Env  Eclipse Juno and JRE is J2SDK 1 5

User · Answer

I use the Eclipse FileSync plugin for live remote debugging  Make sure you tick Allow different target folders  amp  edit the Target folder file setting in the tree view   Setting the Default target folder by the Browse    button without Allow different target folders will set all folders to the same target  I had both libs  amp  classes set to the default for libs so my breakpoints did not update

User · Answer

Same Problem   Easy and Fastest Solution   Just remove All breakpoints in debug perspective and reapply breakpoint  Works like a charm

User · Answer

None of these solutions worked  only changing the workspace worked for me

User · Answer

Make sure  that you are using the correct JRE version to debug your project  Especially if it s a third party project   Also make sure  that there is no trigger point set for any breakpoint

User · Answer

If it doesn t stop even after unchecking SKIP ALL BREAKPOINTS  you can add this android os debug waitfordebugger just before your breakpoint   If you do this your app will definitely wait for debugger at that point everytime even if you are just running your app which it will only find when your device is connected to eclipse   After debugging you must remove this line for app to run properly or else android will just keep waiting for the debugger

User · Answer

I had the same problem  and I found the real cause   I had written some concurrent   multi-threads code  while I added some breakpoints inside the code running in a new thread  So  when JUnit tests ran over  and stopped soon  the code will not reach and stop at the breakpoints    For this situation  we have to click and select  Keep JUnit running after a test run when debugging  check box at  Debug Configurations

User · Answer

I had the same problem when I was using Eclipse Juno   I installed Eclipse Indigo and it works fine  Try to reinstall eclipse

User · Answer

Clearing all Breakpoints fixed the issue  within debugger perspective  Window - gt  Remove All Breakpoints       Rebuilding the project did not work for me

User · Answer

If cleaning and restart machine do not help  the reason may be the default debug port is used by another app  Changing to another value should work  In my case using IBM RAD    Open Administration Console Go to Server Server Types WebSphere application servers  Click link  server1   the default name  Open Java and Process Management Process definition Open Java Virtual Machine  At  Debug arguments   change port number 7777 to the new one Save and restart Server  Done

User · Answer

Please un check this from the Eclipse Menu   Run- Skip all breakpoints   I think this will be enabled permanently once You select the Remove all Break points option in the Debug Breakpoints window

User · Answer

Try to restart eclipse  that works sometimes  I guess there is some kind of cache there

User · Answer

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

User · Answer

Thanks guys  this really saved my day too  I antecedently pressed on skip break points  if you did the same this will result on break point appearing with a backslash icon on them   To bring it back to normal    Switch to Debug perspective  press on the breakpoints view tap --   upper right hand corner of the screen  you also can go there by Window- show view-  breakpoints  5th icon from the left you will see break point with backslash  press on that one    To confirm  try putting break point on any line  and it should appear normally

User · Answer

For me  updating gradle-wrapper jar file worked

User · Answer

Since Eclipse 4 7 Oxygen released in June 2017  there is a new concept of  Triggers for breakpoints   which is displayed as a small  T  next to the breakpoint  blue bullet  icon      All the other breakpoints that are initially suppressed by triggers   will be hit only after any of the trigger points has been hit  All the   triggers are disabled after a trigger point is hit and will be   re-enabled after the run    In order to reset all the  trigger  flags  you need to do the following steps     Switch to Debug perspective   Right-click in the  Breakpoints  view Select  Remove All Triggers     Note   this step does not delete all your breakpoints  which occurs when selecting  Remove All  in the same contextual menu   Note   the keyboard shortcut to enable the triggers is  Alt-R   which takes precedence on the shortcut to open the  Run  menu with its mnemonics  when the  Breakpoints  view is selected

User · Answer

Breakpoints have seemed to work and not-work on the versions of Eclipse I ve used the last couple years  Currently I m using Juno and just experienced breakpoints-not-working again  The solutions above  although good ones  didn t work in my case   Here s what worked in my case    deleted the project check it back out from svn import it into Eclipse again run  mvn eclipse eclipse    Since the project is also a Groovy Http-bulder junit-test project  I had to    convert the project from Java to Groovy add  src test groovy to the Java Build Path  Source folders on build path  include       groovy  on the Java Build Path for  src test groovy

User · Answer

My problem was that my debug view was closed and when I would try to hit a breakpoint  eclipse would just freeze and give me no indication of where it stopped    You can show the Debug View on Mac by clicking Window   Show View   Debug

User · Answer

In my case I had to enable then disable an option in the Preferences  I don t prefer the debug view to keep jumping when a breakpoint is hit so I disabled this option  but caused the issue in question  The solution was to enable it again  start a debug session  the breakpoint is hit and shown in the UI  then disable again the option  Looks like a bug in Eclipse 4 17  UPDATE There is also another simpler way that will make Eclipse show the debugging highlight at the breakpoint or rather refresh the debugging UI to work as it should  After the breakpoint is reached  Eclipse will ask you to switch to debugging mode if you are not already in  click switch button  then activate the debug tab view  you will notice that the stepping buttons are activated and the breakpoint line is highlighted

User · Answer

I suddenly experienced the skipping of breakpoints as well in Eclipse Juno CDT  For me the issue was that I had set optimization levels up  Once I set it back to none it was working fine  To set optimization levels go to Project Properties -  C C   Build -  Settings -  Tool Settings pan depending on which compiler you are using go to -  Optimization and set Optimization Level to  None  -O0   Hope this helps  Best

User · Answer

Perhaps you have pushed the Skip all Breakpoints button in the Breakpoints view

[eclipse] Eclipse doesn't stop at breakpoints

Examples related to eclipse

Examples related to debugging