Arm7 Remote Debug

[james10174]

Not sure if I got all the debug setting right but it's not stopping at the markers. Trying a simple console java helloworld. The debugger attaches to host it seems.

java -jar -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y ${current.project.path}/target/*.jar

pom file.

4.0.0
org.eclipse.che.examples
console-java-simple
jar
1.0-SNAPSHOT
hello-app
http://maven.apache.org


junit
junit
3.8.1
test





org.apache.maven.plugins
maven-compiler-plugin
2.4

true
source



org.apache.maven.plugins
maven-jar-plugin
2.4



true
lib/
org.eclipse.che.examples.HelloWorld

[ghost]

@james10174 Can you try adding a threadsleep of 1-2 seconds before printing Hello World in your class? We do have have such an issue with a remote debug - the java gets executed quicker than the debugger manages to get breakpoints. It's a known issue and it will be fixed.

[james10174]

@eivantsov Didn't work.

I also put the following into the terminal and re-ran without success.

echo "set remotetimeout 10" > ~/.gdbinit

[ghost]

@james10174 I was able to reproduce it on my side with Java debugger. Investigating.

This is a known issue (current master). What version do you have?

[james10174]

@eivantsov I use the java debugger, jdk1.8.0_91 (container and host) and eclipse-che-4.3.0-RC1-SNAPSHOT.

[ghost]

If you use 4.2.2 there's no such an issue there. It's being fixed in master so if you grab the latest nightly in a couple of days, it should be ok.

[james10174]

@eivantsov I will wait for the new nightly. Just let me know when it's ready. Thanks.

[james10174]

@eivantsov Any progress on this issue?

[ghost]

@james10174 worked for me with the latest master. Give ti a shot with a nightly build

[james10174]

@eivantsov It works. Good job :)