| Java remote debug - can't step in [message #250493] |
Mon, 07 January 2008 19:52  |
Eclipse User |
|
|
|
Originally posted by: george.foster.ieee.org
I am having problems using the remote debug capability. The debugger
connects just fine and Eclipse gives my the first executable line in the
debug perspective. I can step into methods in classes in the same JAR as
the starting file, but am unable to step into any classes that are in any
of the other JARs in the classpath. Instead of stepping in, they are
executed as if I chose step over.
Some background before going any further:
My java code is actually executed through Java Invocation interface from
C/C++ code. I start up using the following debug VM args:
-Xrunjdwp:transport=dt_socket,server=y,address=8787,suspend= y
The JAR files referenced using the -Djava.class.path= VM arg are the same
as the ones in the Source tab in the debug launch parameters in Eclipse,
although the class path is rather long (if that is important).
Another interesting symptom: when I am stopped in the debugger, and I try
to "Show In..." and then "Package Navigator", Eclipse cannot bring up the
code. Needless to say, any breakpoints I set are not hit either. I have
tried using Eclipse 3.2.2 and Europa (I get a message about removing
filters when I try the Show in using Europa, but it still can't find the
package).
Any ideas, whether my "stupidity" or something more subtle with the remote
debugger?
Thanks,
George
|
|
|
|
|
|
|
|
| Re: Java remote debug - can't step in [message #251753 is a reply to message #250493] |
Sat, 01 March 2008 11:21  |
| Eclipse User |
|
|
|
Originally posted by: thunderaxiom.gmail.com
George Foster skrev den 08-01-2008 01:52:
> I am having problems using the remote debug capability. The debugger
> connects just fine and Eclipse gives my the first executable line in the
> debug perspective. I can step into methods in classes in the same JAR as
> the starting file, but am unable to step into any classes that are in
> any of the other JARs in the classpath. Instead of stepping in, they are
> executed as if I chose step over.
I have earlier found this to be the problem if for some reason Eclipse
maps your source in which you put the breakpoint to another class than
the one found in the remote session or the breakpoint goes in an
incorrect position.
You may be able to get around the source mapping problem by placing a
method breakpoint instead of a source breakpoint. IIRC this can be done
by right clicking the method in the outline view (and perhaps in the
package explorer view).
If this doesn't help, can you create a minimal case showing the
behaviour and make it available to us?
--
Thorbjørn
|
|
|
Powered by
FUDForum. Page generated in 0.03127 seconds
Home