Bug 27710

Summary:	Entry point not found SetLayout in GDI32
Product:	[Eclipse Project] Platform	Reporter:	Knut Radloff <knut_radloff>
Component:	SWT	Assignee:	Christophe Cornu <christophe.cornu+eclipse>
Status:	RESOLVED FIXED	QA Contact:
Severity:	blocker
Priority:	P1	CC:	dave.gabol, jbraeuchi, matt
Version:	2.0
Target Milestone:	2.1 M4
Hardware:	PC
OS:	Windows NT
Whiteboard:

Description Knut Radloff

2002-12-04 17:24:05 EST

build 20021204
WinNT 4 SP 6

When I start Eclipse with IBM JRE I get a walkback and a message box indicating 
that the GDI32 dll is missing the SetLayout entry point.
The splash screen pops up and stays after the VM dies.
When I run with J9 the VM dies silently. It walks back but I don't see it 
unless I run from command line.
M3 works.

Comment 1 Knut Radloff

2002-12-04 17:25:00 EST

This is my command line and the walkback I get with IBM JRE 1.4

[g:\images\eclipse]java -classpath startup.jar org.eclipse.core.launcher.Main -d
ev bin -update -data g:\images\workspaces\platform-ui
java.lang.UnsatisfiedLinkError: 
G:\Images\eclipse\plugins\org.eclipse.swt.win32_2.1.0\os\win32\x86\swt-win32-
2119.dll: The specified procedure could not be found
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1951)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1807)
        at java.lang.Runtime.loadLibrary0(Runtime.java:805)
        at java.lang.System.loadLibrary(System.java:883)
        at org.eclipse.swt.internal.Library.loadLibrary(Library.java:104)
        at      at org.eclipse.swt.internal.win32.OS.<clinit>(OS.java:42).null
(Unknown Source)
        at org.eclipse.swt.widgets.Display.internal_new_GC(Display.java:1178)
        at org.eclipse.swt.graphics.Device.init(Device.java:541)
        at org.eclipse.swt.widgets.Display.init(Display.java:1197)
        at org.eclipse.swt.graphics.Device.<init>(Device.java:90)
        at org.eclipse.swt.widgets.Display.<init>(Display.java:287)
        at org.eclipse.swt.widgets.Display.<init>(Display.java:283)
        at org.eclipse.ui.internal.Workbench.run(Workbench.java:1369)
        at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:841)
        at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:61)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:40)
        at java.lang.reflect.Method.invoke(Method.java:335)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
        at org.eclipse.core.launcher.Main.run(Main.java:703)
        at org.eclipse.core.launcher.Main.main(Main.java:539)

Comment 2 Matthew Conway

2002-12-04 17:50:25 EST

I have the same problem - described it in Bug 27618.
The problem was also described in Bug 27647 (marked as a duplicate of Bug 27618)

Comment 3 Knut Radloff

2002-12-04 18:05:34 EST

Matt, are you running on NT as well?
This problem is not related to bug 27618. Bug 27618 is about the update manager 
problem which was mentioned on the eclipse-dev mailing list.
Bug 27647 should not be marked as a dup although the early information in 27618 
suggested it is a dup. 
In general, you can always reopen bugs if you think you still see the problem.

Comment 4 Matthew Conway

2002-12-04 18:08:29 EST

Yes, running NT4.0 SP6a

Comment 5 Jesper Kamstrup Linnet

2002-12-05 03:34:35 EST

It works well in I200211271305, but broke in the integration build from Dec. 3.
I'm using Sun JDK1.4.1_01. I'm using Windows NT 4.0 SP 6.

Comment 6 Christophe Cornu

2002-12-05 09:20:04 EST

Chrix to investigate and advise

Raising priority to P1.

Comment 7 Christophe Cornu

2002-12-05 10:38:54 EST

Fix released in HEAD. Fix available in version v>20021205

Comment 8 Sonia Dimitrov

2002-12-05 21:24:59 EST

*** Bug 27768 has been marked as a duplicate of this bug. ***