Bug 149916

Summary:

Internal error during refactoring

Product:

[Eclipse Project] JDT

Reporter:

Davor Cubranic <davor.cubranic>

Component:

Core

Assignee:

JDT-Core-Inbox <jdt-core-inbox>

Status:

RESOLVED INVALID

QA Contact:

Severity:

normal

Priority:

Keywords:

needinfo

Version:

3.2

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Error log showing the exception trace	none

Description Davor Cubranic

2006-07-06 18:37:20 EDT

Eclipse 3.2RC6

I somehow got Eclipse into a state where any refactoring on one class causes an "unexpected exception" error message. I'm attaching the log for one such case.

Comment 1 Davor Cubranic

2006-07-06 18:38:11 EDT

Created attachment 45886 [details]
Error log showing the exception trace

Comment 2 Jerome Lanneluc

2006-07-07 01:56:26 EDT

Moving to JDT UI

Comment 3 Martin Aeschlimann

2006-07-11 09:09:28 EDT

I guess you don't have a reproducible case here.

From the stack trace it seems that ITypeBinding.getJavaElement() returned a IMethod.
We make the assumption that ITypeBinding.getJavaElement() an only be a IType (or null).

Comment 4 Frederic Fusier

2006-07-11 10:05:16 EDT

Does it also happen with 3.2 release (ie. build ID M20060629-1905)?
If you can reproduce with this build, then we definitely need a test case to be able to understand what is exactly happening here...

Comment 5 Davor Cubranic

2006-07-11 13:59:15 EDT

Sorry, no reproducible case, it was a one-time occurrence and I only had the log file.

I'm not using 3.2 yet.

Comment 6 Frederic Fusier

2006-07-12 03:20:54 EDT

OK, so close as REMIND.
Please reopen if you get it again. Then provide a test case and build ID, thanks

Comment 7 Davor Cubranic

2006-07-12 13:49:16 EDT

(In reply to comment #6)
> Please reopen if you get it again. Then provide a test case and build ID,

I will, if I get it again. However, I highly doubt that there will be a nice reproducible test case, as I haven't been able to pinpoint it this time around either, and once Eclipse was restarted, everything started working again. Do you have any advice on what to do if I see this again in order to collect as much information for you guys as possible?

Comment 8 Frederic Fusier

2006-07-14 07:08:48 EDT

Information we need is:
1) the build ID you used when the problem occured
2) the content of .log file to see if there are some exception traces
   (this file is located in <wksp dir>/.metadata subdirectory)
3) of course a test case, but I know this is not always possible...

Comment 9 Denis Roy

2009-08-30 02:05:28 EDT

As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.