Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318334 - Debug mode stops with a ClassNotFound Exception on every constructor, even basic ones like String
Summary: Debug mode stops with a ClassNotFound Exception on every constructor, even ba...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-29 10:28 EDT by Tomer Sagi CLA
Modified: 2020-02-23 13:08 EST (History)
0 users

See Also:

Attachments
Screenshot of debugger when it halts (38.13 KB, image/jpeg)
2010-06-29 10:32 EDT, Tomer Sagi CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomer Sagi CLA 2010-06-29 10:28:21 EDT 
Build Identifier: 20090920-1017

I upgraded the JRE from 1.4.2 to 1.5.0_15 and ever since then I'm getting ClassNot Found errors stopping the debugger on every object constructor, even basic objects like String and Long. Hitting resume (F8) just moves it to the next object constructor and gives the same ClassNotfound error. My code runs fine but the frequent stops are annoying as hell and I can't debug like this. 

Reproducible: Always
Comment 1 Tomer Sagi CLA 2010-06-29 10:32:17 EDT 
Created attachment 173004 [details]
Screenshot of debugger when it halts
Comment 2 Eclipse Genie CLA 2020-02-23 13:08:04 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.