| Eclipse IDE -- view local variables Expressions in .jar file [message #504994] |
Thu, 24 December 2009 03:21  |
Eclipse User |
|
|
|
Hi, all:
My java project relies on several .jar files.
I'd love to debug into it and I managed to do so after attaching the source code folders which actually produce those .jar files.
However, how can I view some of the local variables in some functions of the attached source code, in Expressions view ???
I succeeded in putting "this" into Expressions view, and I managed to view the member variables of this class. However, for some local variables in some functions of the source code folders, I failed to view them.
Well, by the way, I've got to say that I am able to view local variables of my own code. I only can't view values of local variables of the attached source code for some .jar files.
Anybody has the same experience and have you got any work around?
Best Regards
JIA
|
|
|
| Re: Eclipse IDE -- view local variables Expressions in .jar file [message #505023 is a reply to message #504994] |
Thu, 24 December 2009 10:22  |
| Eclipse User |
|
|
|
On 12/24/09 3:21 AM, JIA Pei wrote:
>
>
> Hi, all:
>
> My java project relies on several .jar files.
> I'd love to debug into it and I managed to do so after attaching the
> source code folders which actually produce those .jar files.
>
> However, how can I view some of the local variables in some functions of
> the attached source code, in Expressions view ???
>
> I succeeded in putting "this" into Expressions view, and I managed to
> view the member variables of this class. However, for some local
> variables in some functions of the source code folders, I failed to view
> them.
>
> Well, by the way, I've got to say that I am able to view local variables
> of my own code. I only can't view values of local variables of the
> attached source code for some .jar files.
>
> Anybody has the same experience and have you got any work around?
The .class files in the JAR need to have been compiled with a compiler
option to include debug info in them (I think it's -g); if they were
not, then you get the reduced debugging experience that you're seeing.
There's nothing Eclipse can do when working with JARs that don't include
the debug info.
The .class files that Eclipse produces itself include debug info by
default, which is why it works correctly for your own code.
Do you have any way to re-build the JARs yourself? If so, you could try
modifying the build to include the debug info.
Hope this helps,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.04727 seconds
Home