Bug 206352

Summary:	Resilient class file reader
Product:	[Eclipse Project] JDT	Reporter:	Jerome Lanneluc <jerome_lanneluc>
Component:	Core	Assignee:	Olivier Thomann <Olivier_Thomann>
Status:	VERIFIED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	Olivier_Thomann, srikanth_sankaran
Version:	3.3
Target Milestone:	3.6 M5
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Jerome Lanneluc

2007-10-15 12:39:43 EDT

I20071010-1200

Bug 195823 shows that we are sensitive to the class file format. As we are resilient for .java files that have syntax errors, we should be resilient to .class files that have class file format problems.

One way to implement that would be to keep the existing class file reader, but catch ClassFormatException in its API methods and call a resilient class file reader. This way we would keep the performance of the existing class file reader and be more resilient.

Comment 1 Olivier Thomann

2009-06-26 11:21:33 EDT

I think handling class format exception in the binary indexer is good enough. Having a resilient class file reader means we would somehow "trust" part of the class file before it is corrupted.
If a class file is corrupted, we should not rely on any information it provides.
I would close as WONTFIX.
This is fine for you, Jérôme?

Comment 2 Olivier Thomann

2009-12-09 10:48:14 EST

Closing as WONTFIX.

Comment 3 Srikanth Sankaran

2010-01-25 01:11:44 EST

Verified for 3.6M5