Eclipse - debugger doesn't stop at breakpoint

Question

I am trying to trouble shoot a JUnit. In the source code, I have set break point in two places: 1) in a line where a static member is initialized 2) the first line of one of the test cases.

The debugger stops in the static field initializing line. But it doesn't stop in the test case. No matter where I set the break point in the test case, the debugger doesn't stop there. I know for sure that the test case is executed as I can see the log messages that I have added appear in the log.

Any help would be greatly appreciated.

I am using Eclipse Galileo and JUnit4 launcher.

Can you also add information about which version of JUnit and the JRE you are using? I believe that is helpful in this context. — Vineet Reynolds, Sep 03 '09 at 01:05
The JDK in use is more important by the way (there are some messed JDKs that could cause this). Please ignore the query on the version of JUnit. — Vineet Reynolds, Sep 03 '09 at 01:11
Hmm try downgrading to JDK 5, or a lower version of JDK 6 (definitely not 13), or switch to parallel scavenging GC. — Vineet Reynolds, Sep 03 '09 at 01:39
Is your code compiled with the -g option turned on to generate the debug information in the .class file? That's required, of course. — duffymo, Sep 03 '09 at 00:35

score 103 · Answer 1 · answered Apr 16 '12 at 15:03

103

Fix could be as simple as clicking run/skip all breakpoints. Worked for me.

answered Apr 16 '12 at 15:03

user1164035

1,101
2
7
5

3

it took me three days to spot that I'd somehow clicked that – henry Jul 24 '13 at 19:37
1

Thanks...must have clicked that toolbar icon by accident somehow :-P – kenyee Oct 21 '13 at 23:26
4

Thanks... no idea when that got clicked – njfife Jul 28 '14 at 21:47
1

Thank you so much. For other users, in this situation if you make a breakpoint it will appear slashed. – saurabheights May 28 '16 at 19:14
Same happened to me. I never clicked it...!! Version: Mars Release (4.5.0) Build id: 20150621-1200 – Beezer Jul 26 '16 at 09:59

score 53 · Answer 2 · answered Jun 14 '12 at 20:11

53

Make sure, under Run > Debug Configurations, that 'Stop in main' is selected, if applicable to your situation.

answered Jun 14 '12 at 20:11

Answerer

539
4
2

1

Please be sure to read previous responses before posting. The problem was their jvm version .. and was solved three years ago. Best not to revive old threads unless your response contributes something significant, that was not already covered in previous answers. – Leigh Jun 15 '12 at 02:53
7

Thanks. @Answerer your answer solved my problem. It's strange that "Stop in main" was unset. – Yu Shen Dec 08 '12 at 06:09
26

It appears that his answer did contribute something significant that was not already covered in previous answers :) – scubbo Mar 20 '13 at 11:53
Note, this is an option for Java applications but not Android applications. – Noumenon Jul 13 '13 at 21:41

Vineet Reynolds · Accepted Answer · 2009-09-03T01:23:30.937

39

This could be related to one of the bugs in JDK 6 Update 14, as indicated in the release notes for JDK 6 update 15.

If this indeed turns out to be the issue, you should move to a higher version of the JDK (that's no guarantee though, since fixes have been released against 6u16, 6u18 and 7b1). The best bet is to use -XX:+UseParallelGC flag. Increasing the size of the minimum and maximum heap size, to delay the first GC, bring temporary relief.

By the way, use this bug report in Eclipse to track how others have been faring.

edited Sep 03 '09 at 01:23

answered Sep 03 '09 at 01:15

Vineet Reynolds

76,006
17
150
174

1

I upgraded to JDK 1.6 update 16. Now it stops at all the break points that I have set. Thanks a lot for your help. – Roy Sep 03 '09 at 02:43
You're welcome. u16 seems to be the release where this was fixed to a good enough extent, despite u15's release notes. – Vineet Reynolds Sep 03 '09 at 02:44
Thanks @Vineet - I was pulling my hair out over this one :-) – Jim Garrison Dec 01 '09 at 17:13
@VineetReynolds: I have seen your valuable answers relate to Jboss and Java ee 6. can you help me trouble shoot this problem? http://stackoverflow.com/questions/28954323/error-while-deploying-simple-web-app-in-jboss-as-6-and-jboss-as-7 – brain storm Mar 10 '15 at 18:55

score 23 · Answer 4 · answered Feb 16 '17 at 09:21

23

You might have accidentally skipped all break points in Eclipse toolbar. To fix this go to Eclipse -> Run -> Skip All Breakpoints.

answered Feb 16 '17 at 09:21

Jigna.Shah

231
2
2

2

Arggh, there is a shortcut for this too, I most probably did not accidentially check a menu item, but I am rather likely to have hit Ctrl+Alt+B. Thanks anyways. – Patru Feb 05 '20 at 15:56

score 21 · Answer 5 · edited Dec 27 '22 at 04:27

21

Usually when this happens to me (rare but it does) means that the code being executed is different than the code in the editor. It will happen from time to time for Eclipse that the built classes and the code in editor are out of sync. When that happens I get all sort of weird debugger behavior (debugging empty lines, skipping lines of code etc).

Restarting Eclipse, clean all projects and rebuild everything usually clears things up. I had also the Maven plugins (older versions... had not had it for a while now) that had a tendency to do that too.

Otherwise it might be a bug, maybe the one Vineet stated,

Hope this helps

edited Dec 27 '22 at 04:27

starball

20,030
7
43
238

answered Sep 03 '09 at 03:00

Newtopian

7,543
4
48
71

Yea, what you've stated happens more in IDEs that do not automatically recompile code. Oracle JDeveloper (from personal experience) and to a lesser extent (Netbeans) have been found wanting. – Vineet Reynolds Sep 03 '09 at 05:03
1

Good advice. Not said enough. Sometimes we over-think the problem and it's just the system out of synch. Such as it is with rebooting a computer for trouble shooting simple issues. – Xonatron Jun 25 '12 at 19:18
Thanks, that was the problem in my case. It sounds stupid, but a simple clean and F5 after a build did the job. – jfajunior May 27 '19 at 14:35

score 4 · Answer 6 · answered Jun 04 '17 at 21:14

4

In my case the problem was that I hadn't Debug view open in Debug perspective, so:

1 - Be sure you have debug perspective opened:

2 - Be sure you have debug view opened:

answered Jun 04 '17 at 21:14

Dani

1,825
2
15
29

score 3 · Answer 7 · answered Apr 02 '15 at 10:41

3

Project -> Clean seemed to work for me on on JRE 8

answered Apr 02 '15 at 10:41

JH95

489
1
7
24

sergeyan · Answer 8 · 2016-10-17T16:01:35.867

In order to debugger work with remote, the java .class files must be complied along with debugging information. If "-g:none" option was passed to compiler then the class file will not have necessary information and hence debugger will not be able to match breakpoints on source code with that class in remote. Meanwhile, if jars/class files were obfuscated, then they also will not have any debug info. According to your responses, most probably this is not your case, but this info could be useful for others who face the same issue.

score 2 · Answer 9 · answered Dec 18 '17 at 16:40

2

Remove all breakpoints and re-add them.

answered Dec 18 '17 at 16:40

Raffi Khatchadourian

3,042
3
31
37

This fixed it for me. Weird. Thx – Atom999 Jan 23 '19 at 21:52

score 1 · Answer 10 · answered Jul 31 '13 at 06:57

1

For JDK7, run->Debug Configurations, check "Keep JUnit running after a test run when debugging".

answered Jul 31 '13 at 06:57

Frank Fu

778
4
8
12

score 1 · Answer 11 · answered Dec 12 '13 at 14:18

1

Happened to me once, when I had unchecked "Run > Build automatically" and forgot to re-check it.

answered Dec 12 '13 at 14:18

Mathiouss

101
7

score 1 · Answer 12 · answered Jun 25 '14 at 16:15

Make sure you declare the package at the top. In my groovy code this stops at breakpoints:

package Pkg1

import java.awt.event.ItemEvent;

isMule = false

class LineItem {
    // Structure defining individual DB rows
    public String ACCOUNT_CODE
    public String ACCOUNT_DESC
...

This does not stop at breakpoints:

import java.awt.event.ItemEvent;

isMule = false

class LineItem {
    // Structure defining individual DB rows
    public String ACCOUNT_CODE
    public String ACCOUNT_DESC
...

After struggling a lot this solve my problem. Thanks +1 – Federico Piazza Apr 16 '15 at 21:45 — Federico Piazza, Apr 16 '15 at 21:45

score 0 · Answer 13 · edited Jul 21 '14 at 21:45

0

To remove the breakpoints:

Debug your class as a junit test
When your debugger stops, click the "breakpoints" tab next to "variables" and "expressions"
At the top right of the breakpoint tab, click the button with two 'X'
Stop the test, replace your breakpoint and run the debugger again

edited Jul 21 '14 at 21:45

Jamal

763
7
22
32

answered Jul 21 '14 at 21:25

Cyrois

439
4
9

score 0 · Answer 14 · edited Dec 17 '18 at 13:56

0

One additional comment regarding Vineet Reynolds answer.

I found out that I had to set -XX:+UseParallelGC in eclipse.ini

I setup the virtual machine (vm) arguments as follows

-vmargs
-Dosgi.requiredJavaVersion=1.7
-Xms512m
-Xmx1024m
-XX:+UseParallelGC
-XX:PermSize=256M
-XX:MaxPermSize=512M

that solved the issue.

edited Dec 17 '18 at 13:56

rsp

23,135
6
55
69

answered Jul 24 '14 at 19:18

Amir Pauker

56
4

score 0 · Answer 15 · edited Feb 15 '16 at 11:16

0

If nothing works-

Remove that Remote/Local Debug Configuration, and Create a new One.
Add the Source in Debug Configurations.

edited Feb 15 '16 at 11:16

Mohammad Faisal

5,783
15
70
117

answered Feb 04 '15 at 23:13

kanaparthikiran

523
12
15

score 0 · Answer 16 · answered Apr 09 '15 at 08:45

Also verify if breakpoints on other lines DO work, it may be a bug in the debugger. I have had a problem with the Eclipse debugger where putting a breakpoint on a boolean assignment whose code was on the next line didn't work I reported this here, but putting it on the previous or next line did.

score 0 · Answer 17 · answered May 12 '16 at 08:41

Another possible problem is that the debugger port may be blocked by the firewall. For example, I was using mule anypoint studio (v 5.4.3). The default debugger port is 6666. When a flow is executed, it would not stop at breakpoint. when I changed the port to another (e.g. 8099), it worked fine.

score 0 · Answer 18 · answered May 25 '16 at 10:10

0

Go to Right click->Debug Configuration and check if too many debug instances are created. My issue was resolved when i deleted multiple debug instances from configuration and freshly started debugging.

answered May 25 '16 at 10:10

priyanka_rao

465
1
4
20

score 0 · Answer 19 · answered Aug 13 '16 at 11:51

0

If you are on Eclipse,

Right click on your project folder under "Package Explorer".

Goto Source -> Clean up and choose your project.

This will cleanup any mess and your break-point should work now.

answered Aug 13 '16 at 11:51

Sureshbabu E

91
2
4

score 0 · Answer 20 · answered Jan 30 '17 at 22:10

0

Creating a new workspace worked for me.

answered Jan 30 '17 at 22:10

Ahmed Tawila

988
2
13
20

score 0 · Answer 21 · answered Mar 21 '17 at 08:38

In my case I had multiple projects in same workspace. The java file I was trying to debug was present in more than one projects with same package.

I didn't need the other project, so simply closed unrelated projects (or remove the file from unrelated project).

Tanorix · Answer 22 · 2021-08-26T14:20:49.047

0

It happened to me when I had several project, I realized that I created a spring boot configuration of a project B from a project A (I clicked on Duplicate and change the parameter to have a config for the project B) and in that case I haven't the debug mode so I removed this config and I created directly a new one by clicking New in Spring Boot App

edited Aug 26 '21 at 14:20

answered Aug 26 '21 at 14:13

Tanorix

230
2
16

Francisco Corrales Morales · Answer 23 · 2015-02-18T16:41:55.997

-3

This is what works for me:

I had to put my local server address in the PHP Server configuration like this:

enter image description here

Note: that address, is the one I configure in my Apache .conf file.

Note: the only breakpoint that was working was the 'Break at first line', after that, the breakpoints didn't work.

Note: check your xdebug properties in your php.ini file, and remove any you think is not required.

edited Feb 18 '15 at 16:41

answered Feb 18 '15 at 16:30

Francisco Corrales Morales

3,676
1
37
64

1

I fail to see how this answers the question (about JUnit and Java debugging) – Newtopian Sep 29 '16 at 17:23

Eclipse - debugger doesn't stop at breakpoint

23 Answers23

Linked