Skip to main content

Breakpoints don't work with 6u14?

11 replies [Last post]
kutzi
Offline
Joined: 2005-03-29

Hi,

I've spotted the strange behaviour that breakpoints doesn't seem to work when debugging with Java 6u14 (b01 or b03). When I change the launch configuration to Java 6u11, breakpoints work fine. This is with Eclipse 3.4.2

Has anyone else experienced this?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kutzi
Offline
Joined: 2005-03-29

> It's probably more a disconnect from the Eclipse
> side. Eclipse may not be evolving as fast as Java
> is. The first thing that has to happen is that Java
> reaches a more or less final release for 1.6 And
> then Eclipse has to be recompiled and altered and
> updated to conform to or support 1.6.
> I personally use 1.5.0.16 (I think) to run Eclipse
> and never have problems. I also still compile to 1.5
> to let more people run my applet.

Why should the debugger API change in an update release to the JVM?
I don't see how this could possibly be an Eclipse problem.
As I've said it works fine with Java 6 Update 11.

Haven't tried it with the final release of 6u14, though.

demonduck
Offline
Joined: 2008-03-14

> > It's probably more a disconnect from the Eclipse
> > side.
>
> Why should the debugger API change in an update
> release to the JVM?

Why indeed? At this point in the history of Java, you just cannot count on the stability of any of the API's.

kutzi
Offline
Joined: 2005-03-29

> > > It's probably more a disconnect from the Eclipse
> > > side.
> >
> > Why should the debugger API change in an update
> > release to the JVM?
>
> Why indeed? At this point in the history of Java,
> you just cannot count on the stability of any of the
> API's.

If it would be a change in Java 7, I'd agree. But this has been in an update release to the stable release 6. And such an update should not change an external API - at least not in a way that breaks existing applications.
SO my point was that this most probably was (is?) a bug in JDK 6u14 and not in Eclipse.

demonduck
Offline
Joined: 2008-03-14

> SO my point was that this most probably was (is?) a
> bug in JDK 6u14 and not in Eclipse.

That's as good as any other guess...

autoboxing
Offline
Joined: 2009-06-09

Same problem here with Eclipse 3.4.2 (final) and Eclipse 3.5 RC3 (both on Win XP SP3)

Going back to 6u13 solved the problem for now, so there seems to be a change in 6u14.

AB

autoboxing
Offline
Joined: 2009-06-09

It seems to be a bug in the JDK.

See here for a repro without Eclipse:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=279137#c14

ndcosta123
Offline
Joined: 2007-10-03

There is a bug created to track this behavior and is visible at
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6862295

We have listed a workaround for this problem, which can be used while we investigate a fix for the bug.

Work Around
Using the option -XX:+UseParallelGC makes the failure not
reproducible with either the Client VM or the Server VM.

Thanks,
Nelson

the_8tre
Offline
Joined: 2004-07-08

Hi,

I got the same problem.
If I use Java 6u14 (b03 or b04) in Eclipse my breakpoints are very rarely respected.
If I go back to Java 6u12 everything works fine.
I experienced that with eclipse 3.3 and Eclipe 3.4.

It would be nice if anyone could have a look at this problem.

demonduck
Offline
Joined: 2008-03-14

It's probably more a disconnect from the Eclipse side. Eclipse may not be evolving as fast as Java is. The first thing that has to happen is that Java reaches a more or less final release for 1.6 And then Eclipse has to be recompiled and altered and updated to conform to or support 1.6.

Up to now -- as far as I know -- Eclipse has been developed with 1.5. I'm probably not the best one to comment on this though because I'm not really involved with Eclipse other than as an every day user.

I personally use 1.5.0.16 (I think) to run Eclipse and never have problems. I also still compile to 1.5 to let more people run my applet.

the_8tre
Offline
Joined: 2004-07-08

Does anyone know where we can report this kind of problem on the Eclipse side ?
I got to compile my projects using Java 6 and I'm sure that people that are in the same case would be glad if this problem could be addressed as soon as possible before the final update 14 release :-)

Any pointer ?

demonduck
Offline
Joined: 2008-03-14

This would be a good place to start:

http://www.eclipse.org/