Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 395285

Summary:	Unable to step into Swing source in debugger
Product:	[Eclipse Project] JDT	Reporter:	Malcolm Storey <malcolm.storey>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	malcolm.storey, Michael_Rennie
Version:	4.3	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Malcolm Storey

2012-11-28 09:03:41 EST

The debugger refuses to step into (eg) Swing source code in the debugger and takes me to AppContext.class - Class File Editor - Source not found.

It steps through my own source code quite happily.

From the source, F3 takes me into the Swing source correctly - presumably this means it's correctly installed.

From the debugger, F3 takes me into the Swing source correctly.

Breakpoints in both my own code and Swing source will halt processing and bring up the source (including Swing code), but any attempts to step take me back to my own code.

The only unusual thing is that I'm running from an account that doesn't have admin privileges. I installed Java from the Admin account. Maybe the debugger is trying to open the Swing source files with write permission?

Comment 1 Malcolm Storey

2012-11-29 13:36:20 EST

This problem appeared when I upgraded to Juno.

Now running Version: 4.2.1
Build id: M20120914-1800

Comment 2 Malcolm Storey

2015-08-04 07:49:36 EDT

This was ages ago. My fault for not setting up libraries correctly. (It'd help if Eclipse refused to accept libraries it couldn't read.)