| Debug Java API core classes in Eclipse [message #60821] |
Thu, 05 May 2005 16:01  |
Eclipse User |
|
|
|
Originally posted by: Davyd.Matthys.UGent.be
Today I've been busy reading a bit about security in Java. The usage of
policy files and the security manager seem somewhat obscure to me. Not of
a problem, I thought: I'll write a simple class with Eclipse, and then use
the debugging features to discover more.
Sounds nice, except for one thing. Apparently, it is not possible to debug
the core classes of the Java API. Suppose for example that in my class,
I've come to a line with the following code:
list.add(new Integer(31)); // list is an ArrayList object.
OK, now I want to use the "Step INTO" operation, to go into the internals
of the add method of the ArrayList class. But Eclipse won't buy it: if I
want to do this, the result I get is exactly the same as when I would have
chosen the "Step OVER" operation.
A core Java class isn't that much different from e.g. a class one would
write himself, isn't it? I've tried this on 4 different versions of
Eclipse: 2.1.3, 3.0.1, 3.0.2 and the most recent milestone 3.1M6. None of
them gave me a satisfactory result.
My question to my colleagues: is this inherent in Eclipse? Do we have any
workaround available? Any help and/or comments would be mostly
appreciated! Maybe this is more of a developer question, but IMHO this
newsgroup would be a good place to start it ;)
Many thanks and kind regards,
David.
|
|
|
| Re: Debug Java API core classes in Eclipse [message #60824 is a reply to message #60821] |
Thu, 05 May 2005 18:25  |
| Eclipse User |
|
|
|
Originally posted by: manahan.NOSPAM.ca.ibm.com
David wrote:
> Today I've been busy reading a bit about security in Java. The usage of
> policy files and the security manager seem somewhat obscure to me. Not
> of a problem, I thought: I'll write a simple class with Eclipse, and
> then use the debugging features to discover more.
>
> Sounds nice, except for one thing. Apparently, it is not possible to
> debug the core classes of the Java API. Suppose for example that in my
> class, I've come to a line with the following code:
>
> list.add(new Integer(31)); // list is an ArrayList object.
>
> OK, now I want to use the "Step INTO" operation, to go into the
> internals of the add method of the ArrayList class. But Eclipse won't
> buy it: if I want to do this, the result I get is exactly the same as
> when I would have chosen the "Step OVER" operation.
> A core Java class isn't that much different from e.g. a class one would
> write himself, isn't it? I've tried this on 4 different versions of
> Eclipse: 2.1.3, 3.0.1, 3.0.2 and the most recent milestone 3.1M6. None
> of them gave me a satisfactory result.
>
> My question to my colleagues: is this inherent in Eclipse? Do we have
> any workaround available? Any help and/or comments would be mostly
> appreciated! Maybe this is more of a developer question, but IMHO this
> newsgroup would be a good place to start it ;)
>
> Many thanks and kind regards,
>
> David.
>
Works for me. It may be that you are a JRE to compile against and JRE's
don't have src.zip. You need a JDK.
Peter
|
|
|
| Re: Debug Java API core classes in Eclipse [message #60943 is a reply to message #60824] |
Fri, 06 May 2005 05:30 |
| Eclipse User |
|
|
|
Originally posted by: Davyd.Matthys.UGent.be
Thanks Peter, you hit the mark exactly right! As you install Java, you got
one private JRE (e:\development\java om my computer) and one public JRE in
de Program Files dir. Eclipse by default chooses the public one. After i
commanded him to perform compilations based on the private one, it worked
very well.
Thanks a lot for you kind and quick reply!
David.
|
|
|
Powered by
FUDForum. Page generated in 0.11967 seconds
Home