Bug 115363 - java.lang.VerifyError in org.eclipse.ui.workbench from HEAD, using N20051107
Summary: java.lang.VerifyError in org.eclipse.ui.workbench from HEAD, using N20051107
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 blocker (vote)
Target Milestone: 3.2 M4   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-07 13:28 EST by Boris Bokowski CLA
Modified: 2005-12-12 11:00 EST (History)
0 users

See Also:


Attachments
class file with the verify error (7.58 KB, application/octet-stream)
2005-11-07 13:29 EST, Boris Bokowski CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Bokowski CLA 2005-11-07 13:28:23 EST
N20051107, fresh workspace, all ui plug-ins and test plug-ins from HEAD.

I created a new "RCP application with intro" using the wizard, deleted its
Activator class, and tried to run it from within Eclipse.

Got this stack trace:

java.lang.VerifyError: (class: org/eclipse/ui/internal/PluginActionSetBuilder,
method: findInsertionPoint signature:
(Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/jface/action/IContributionManager;Z)Lorg/eclipse/jface/action/IContributionItem;)
Illegal target of jump or bran [5
	at
org.eclipse.ui.internal.ActionPresentation.setActionSets(ActionPresentation.java:184)
	at
org.eclipse.ui.internal.WorkbenchWindow.updateActionSets(WorkbenchWindow.java:2552)
	at org.eclipse.ui.internal.WorkbenchWindow$5.run(WorkbenchWindow.java:2374)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
	at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:2337)
	at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.java:678)
	at org.eclipse.ui.internal.Workbench.busyOpenWorkbenchWindow(Workbench.java:680)
	at org.eclipse.ui.internal.Workbench.doOpenFirstTimeWindow(Workbench.java:1321)
	at org.eclipse.ui.internal.Workbench.openFirstTimeWindow(Workbench.java:1227)
	at
org.eclipse.ui.internal.WorkbenchConfigurer.openFirstTimeWindow(WorkbenchConfigurer.java:190)
	at
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:706)
	at org.eclipse.ui.internal.Workbench.init(Workbench.java:1039)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1707)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:376)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
	at snip.intro.Application.run(Application.java:18)
	at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:165)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:338)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
	at org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)
Comment 1 Boris Bokowski CLA 2005-11-07 13:29:57 EST
Created attachment 29454 [details]
class file with the verify error
Comment 2 Olivier Thomann CLA 2005-11-07 15:11:02 EST
The problem comes from the fix for bug 114855.
I didn't manage correctly the case where the first forward reference is greater
than the value in the first forward reference from the other labels and both
collections' size is 1.
I will provide a patch in order to validate the fix.
Comment 3 Olivier Thomann CLA 2005-11-07 15:36:04 EST
Fixed and released in HEAD.
Regression test added in
org.eclipse.jdt.core.tests.compiler.regression.TryStatementTest.test033
Comment 4 Frederic Fusier CLA 2005-12-12 11:00:19 EST
Verified for 3.2 M4 using build I20051212-0010 (we got now a stack trace saying that Activator does not exist...)