Bug 546522 - [Advanced Source Lookup] Debugger stops suprisingly in Premain$1.transform
Summary: [Advanced Source Lookup] Debugger stops suprisingly in Premain$1.transform
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.12   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-17 11:35 EDT by Stefan Baier CLA
Modified: 2023-10-31 16:28 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Baier CLA 2019-04-17 11:35:05 EDT
Every time I step into a constructor call of a new not yet loaded class, the debugger stops at

Premain$1.transform(ClassLoader, String, Class<?>, ProtectionDomain, byte[]) line: 45	


The stacktrace is

Thread [main] (Suspended)	
	owns: Object  (id=42)	
	Premain$1.transform(ClassLoader, String, Class<?>, ProtectionDomain, byte[]) line: 45	
	TransformerManager.transform(ClassLoader, String, Class<?>, ProtectionDomain, byte[]) line: not available	
	InstrumentationImpl.transform(ClassLoader, String, Class<?>, ProtectionDomain, byte[], boolean) line: not available	
	ClassLoader.defineClass1(String, byte[], int, int, ProtectionDomain, String) line: not available [native method]	
	Launcher$AppClassLoader(ClassLoader).defineClass(String, byte[], int, int, ProtectionDomain) line: not available	
	Launcher$AppClassLoader(SecureClassLoader).defineClass(String, byte[], int, int, CodeSource) line: not available	
	Launcher$AppClassLoader(URLClassLoader).defineClass(String, Resource) line: not available	
	URLClassLoader.access$100(URLClassLoader, String, Resource) line: not available	
	URLClassLoader$1.run() line: not available	
	URLClassLoader$1.run() line: not available	
	AccessController.doPrivileged(PrivilegedExceptionAction<T>, AccessControlContext) line: not available [native method]	
	Launcher$AppClassLoader(URLClassLoader).findClass(String) line: not available	
	Launcher$AppClassLoader(ClassLoader).loadClass(String, boolean) line: not available	
	Launcher$AppClassLoader.loadClass(String, boolean) line: not available	
	Launcher$AppClassLoader(ClassLoader).loadClass(String) line: not available	
	Application2.start() line: 41	
	Application2.main(String[]) line: 17
Comment 1 Sarika Sinha CLA 2019-04-22 01:01:24 EDT
@Igor, 
I thought this issue was fixed?
Comment 2 Igor Fedorenko CLA 2019-04-22 07:58:48 EDT
(In reply to Sarika Sinha from comment #1)
> @Igor, 
> I thought this issue was fixed?

Yes, it was fixed last year, iirc. The fix was to step-filter org.eclipse.jdt.launching.internal.* classes by default. The filter is still there in 4.12 M1 (I20190411-0625) and I could not reproduce the problem locally. We'll need example project and exact steps to trigger the problem to troubleshoot this further.
Comment 3 Mary Ann Salvador CLA 2019-11-19 14:16:52 EST
I am still encountering this. How do I get this resolved?
Comment 4 Mary Ann Salvador CLA 2019-11-19 14:17:23 EST
I am still encountering this. How do I get this resolved?
Comment 5 Igor Fedorenko CLA 2019-11-19 14:25:24 EST
(In reply to Mary Ann Salvador from comment #4)
> I am still encountering this. How do I get this resolved?

please provide smalls standalone example project and exact steps to reproduce the problem starting with fresh empty eclipse workspace using latest "Eclipse IDE for Java Developers" or SDK packages.
Comment 6 Eclipse Genie CLA 2021-11-09 00:54:43 EST
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 7 Eclipse Genie CLA 2023-10-31 16:28:35 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.