Bug 299425 - Can't step into JDK code
Summary: Can't step into JDK code
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-12 15:22 EST by Lyle Ziegelmiller CLA
Modified: 2022-06-30 06:42 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lyle Ziegelmiller CLA 2010-01-12 15:22:18 EST
Build Identifier: M20090211-1700

I've spent an entire day trying to get the debugger to step into the source code for JScrollBar. 

I uninstalled the JDK & JRE and src.zip, and installed the latest versions from the sun web site. I made sure src.zip is added under rt.jar and jsse.jar, as well (under Java Build Path, click on Libraries tab, expand rt.jar and jsse.jar). I tried adding src.zip to the source lookup paths under the Libraries tab, and I made sure that src.zip really is present in C\Program Files\Java\jdk1.6.0_17, and it's the latest version, as I just downloaded it along with the JRE and JDK.

I'm not sure what else to do. When I try to step into the source code for JScrollBar, it displays the JScrollBar.java file, but it says in the stack frame:

JScrollBar.<init>(int) line: not available

Even if I'm doing something wrong, it shouldn't be this hard to get it to work, and the diagnostic messages should be a lot better. 

Reproducible: Always

Steps to Reproduce:
1.Invoke debugger
2.Attempt to step into the constructor for JScrollBar, or any other JDK code
Comment 1 Darin Wright CLA 2010-01-26 22:41:08 EST
When I used the JRE, line numbers were not available (likely the class files are not compiled with debug attributes). When I used the JDK, source and line numbers were available.
Comment 2 Lyle Ziegelmiller CLA 2010-01-27 11:47:52 EST
(In reply to comment #1)
> When I used the JRE, line numbers were not available (likely the class files
> are not compiled with debug attributes). When I used the JDK, source and line
> numbers were available.

I'm not sure I understand what you're saying. The JRE is always used when running a Java program. What did you do different, from what I outlined in my original posting, to "use the JDK"?

thanks

Lyle
Comment 3 Darin Wright CLA 2010-01-27 14:37:39 EST
In my "Program Files/Java" directory there is a "jre6" and a "jdk1.6.0_16" directory. If I define a JRE using the "jdk1.6.0_16" directory and use that JRE when running/debugging, I see source.
Comment 4 Lyle Ziegelmiller CLA 2010-01-29 14:22:45 EST
(In reply to comment #3)
> In my "Program Files/Java" directory there is a "jre6" and a "jdk1.6.0_16"
> directory. If I define a JRE using the "jdk1.6.0_16" directory and use that JRE
> when running/debugging, I see source.

Well, I can see the source code in some files, like Component.java (I think), but not others, like JScrollBar.java.   I noticed that even though I downloaded everything fresh, the timestamp on the src.zip file is months older than the other files. I wonder if the latest download simply isn't synchronized with itself.
Comment 5 Eclipse Genie CLA 2020-07-09 05:56:45 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Eclipse Genie CLA 2022-06-30 06:42:58 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.