Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332878

Summary:	eclipse 3.6 return COMException and garbled when calling dll files by jawin
Product:	[Eclipse Project] JDT	Reporter:	xdung <zhngxh>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	RESOLVED NOT_ECLIPSE	QA Contact:
Severity:	critical
Priority:	P3	CC:	daniel_megert, remy.suen
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description xdung

2010-12-17 20:22:13 EST

Build Identifier: 20100617-1415

I have try the jdk from jdk1.6.0_u20 to u23,no matter what jdk version,it get the same exception¡£But,when I change the eclipse version to 3.3,the exception disappeared.
org.jawin.COMException: 0: 2¨´¡Á¡Â3&#633;|¨ª¨º
	at org.jawin.marshal.SharedStubs.invokeIGGI_I(Native Method)
	at org.jawin.FuncPtr.invoke_I(FuncPtr.java:303)
	at demo.HelloDll.main(HelloDll.java:29)
Exception in thread "main" org.jawin.COMException: 0: 2¨´¡Á¡Â3&#633;|¨ª¨º
	at org.jawin.marshal.SharedStubs.invokeIGGI_I(Native Method)
	at org.jawin.FuncPtr.invoke_I(FuncPtr.java:303)
	at demo.HelloDll.main(HelloDll.java:29)

Reproducible: Always

Steps to Reproduce:
1.download the latest Jawin-2.0-alpha1 with the link http://sourceforge.net/projects/jawinproject/files/jawinproject/Jawin-2.0-alpha1/
2.extract the zip file
3.copy file bin/jawin.dll to system32 folder
4.create a new java project,and import the jawin libs(jawin.jar&jawin-stubs.jar)
5.import the demo to our project
6.run HelloDll.java file in the demo

Comment 1 Remy Suen

2010-12-18 08:59:14 EST

Does it work if you run from the command line?

There may be launching differences between the two versions or something with SWT is interfering.

Comment 2 Dani Megert

2011-06-01 08:23:51 EDT

This doesn't look like an Eclipse issue: the exception happens inside the DLL. Also, the text/description that the exception provides is too cryptic to do anything with it.

If you still see the problem using 3.7 RC3 and if it works via command line (see unanswered question in comment 1), then please reopen this bug.

Comment 3 Dani Megert

2011-06-01 08:24:57 EDT

Just a thought: maybe it's an encoding issue?