[chconnor]

Hi there -

I'll try to keep it brief :-)

- editing in Eclipse

- code is also built on a remote server (shared via subversion)

- the program is run on that remote machine

- eclipse debugger attaches to that remote machine/VM via ssh linked local port

- this has all worked perfectly for a long time

- now, setting breakpoints works only sometimes; some points work, some don't. Whether they are checked ("installed") or not seems uncorrelated.

- I'm sure it's connecting to the right VM, that the breakpoints in question should trip, etc

- when it works, it works fine (variables inspectable, etc)

- I'm sure it's the same codebase/jars in both places

- At first it was JDK 1.6 locally and 1.5 remotely, so I installed 1.5 locally and pointed Eclipse to it (there is a slight version difference). No change in behavior.

- remote code is built with ant javac parameter "debug=true", but not the "debuglevel" parameter (wasn't needed before, so...)

- remote code is run with:
java -ea -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,ad dress=<portnum> -jar <myjar>.jar

- I've restarted the whole OS, the eclipse program, refreshed the workspace, rebuilt and restarted the remote code from scratch, etc. No change.

- The workspace .metadata/.log file shows nothing, although previously a couple times I was running through things there were packet timeout errors. I increased the debug timeout value in the eclipse prefs. Nothing now.

- I am running eclipse Version: 3.4.1 Build id: M20080911-1700 in Linux (Kubuntu). Same behavior in WinXP version (slightly older version of eclipse, not sure which)

Anything else I should check/confirm? I'm about to give up!

Many thanks for any ideas!

-Casey

[chconnor]

One more thing - the remote computer is running a 64 bit VM, local is not. Thanks, -c

[chconnor]

update: seems as if the line number correlation is off... e.g. "skip over" will show the next current line of execution in the middle of a few comment lines, etc. Again, I am sure that the code is the same in both places... at least in terms of the raw files (diff shows nothing). Could it be a bug in Eclipse and/or Java or am I overlooking something?