Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332878 - eclipse 3.6 return COMException and garbled when calling dll files by jawin
Summary: eclipse 3.6 return COMException and garbled when calling dll files by jawin
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-17 20:22 EST by xdung CLA
Modified: 2011-06-01 08:24 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description xdung CLA 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ɹ|¨ª¨º
	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ɹ|¨ª¨º
	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 CLA 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 CLA 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 CLA 2011-06-01 08:24:57 EDT 
Just a thought: maybe it's an encoding issue?