Bug 342102

Comment 1 Kentaroh Noji 2011-04-07 01:33:30 EDT

Created attachment 192696 [details]
Error log

This is an error log for this problem.

Comment 2 Dani Megert 2011-04-07 01:48:55 EDT

Hi Kentaroh,

can you attach the VM dump? It should either be a sibling of the eclipse.exe or the java.exe/javac.exe.

Comment 3 Dani Megert 2011-04-07 02:02:22 EDT

>Build Identifier: I20110329-2200
I assume this is a 3.7 build not 4.1 as indicated in the version field?

Comment 4 Dani Megert 2011-04-07 03:38:51 EDT

I only have Japanese 'Kana' on my system (English Windows XP) and that works fine using latest 3.7 build together with JRE 1.6.0 IBM Windows 32 build pwi3260sr9fp1-20110208_03 (SR9 FP1). Unfortunately I don't have a Japanese Windows XP at hand.

Can you provide more exact steps (how/what DBCS do you enter?

Comment 5 Dani Megert 2011-04-07 03:49:08 EDT

(In reply to comment #4)
> I only have Japanese 'Kana' on my system (English Windows XP)
I was able to set the input method to Japanese Input method (MS-IME2002) and switch to Hiragana but was not able to crash the system.

Comment 6 Kentaroh Noji 2011-04-07 05:07:17 EDT

(In reply to comment #3)
>I assume this is a 3.7 build not 4.1 as indicated in the version field?

No, I use I20110329-2200 for 4.1 build. I will attach the screen capture for the id. 

(In reply to comment #4)
>Can you provide more exact steps (how/what DBCS do you enter?
Yes, here are my steps. 

1. Open the context menu on a project you created.
2. New > Untitled Text File
3. Click input mode icon in the windows language bar, and then click Hiragana
4. Enter Hiragana characters in the untitled text. 
5. Then, crash  

I think you can see this problem in my test machine. I have set up my machine so that you can login my machine using remote login. I will send email about the machine information to you.

Comment 7 Kentaroh Noji 2011-04-07 05:17:16 EDT

Created attachment 192708 [details]
screen capture of build id

Comment 8 Dani Megert 2011-04-07 08:10:37 EDT

Please see http://www-01.ibm.com/support/docview.wss?uid=swg21181068#1.1 on how to find the javacore file.

Also, please try this:
1. import the SWT bundles into the workspace (Import > Plug-ins and Fragments)
2. create a new Java project 'A'
3. add the two SWT projects to the Java build path of 'A'
4. paste into 'A':
----------------------------
package snippet;
import org.eclipse.swt.SWT;
import org.eclipse.swt.custom.StyledText;
import org.eclipse.swt.layout.FillLayout;
import org.eclipse.swt.widgets.*;
public class Snippet {
	public static void main (String [] args) {
		Display display = new Display ();
		Shell shell = new Shell (display);
		shell.setLayout(new FillLayout());
		StyledText text = new StyledText (shell, SWT.BORDER);
		text.setText("ABC");
		shell.setSize(200, 200);
		shell.open();
		while (!shell.isDisposed ())
			if (!display.readAndDispatch ()) display.sleep ();
		display.dispose ();
	}
}
----------------------------
5. Run > Run As > Java Application
6. type Japanese Hiragana

Does it also crash?

Comment 9 Kentaroh Noji 2011-04-07 22:33:34 EDT

(In reply to comment #8)
> Please see http://www-01.ibm.com/support/docview.wss?uid=swg21181068#1.1 on how
> to find the javacore file.

I try to find the javacore files, but the files are not found...   

> 5. Run > Run As > Java Application
> 6. type Japanese Hiragana
> 
> Does it also crash?

Yes, the snippet crashed. Is this SWT's problem?.

Comment 10 Dani Megert 2011-04-08 01:57:43 EDT

> Yes, the snippet crashed. Is this SWT's problem?.
Yes.

Comment 11 Felipe Heidrich 2011-04-12 14:53:46 EDT

Fixed in HEAD.

This happened becuase a VtblCall was removed during the work to fix bug 220098.
I added the method back, input method is working again.

Comment 12 Kentaroh Noji 2011-04-19 02:53:38 EDT

(In reply to comment #11)
> Fixed in HEAD.
> 
> This happened becuase a VtblCall was removed during the work to fix bug 220098.
> I added the method back, input method is working again.

Still the same problem happens in I20110412-1532 build (v3.7).

Comment 13 Kentaroh Noji 2011-04-19 02:59:18 EDT

Since the same problem happens in the latest build, I am changing the status from Resolved to Reopened.

Comment 14 Dani Megert 2011-04-19 04:11:58 EDT

> Still the same problem happens in I20110412-1532 build (v3.7).
Please try with a build where the fix is in. The bug got marked as fixed in HEAD on 2011-04-12 20:53:46, so it is impossible that it is in I20110412-1532.

Comment 15 Dani Megert 2011-04-19 04:13:52 EDT

(In reply to comment #14)
> The bug got marked as fixed in HEAD on 2011-04-12 20:53:46
That is "my" time (would be 2011-04-12 14:53:46 build location time) but it's still after the input for the I-build was made.

Comment 16 Kentaroh Noji 2011-04-19 04:17:34 EDT

(In reply to comment #14)
> Please try with a build where the fix is in. The bug got marked as fixed in
> HEAD on 2011-04-12 20:53:46, so it is impossible that it is in I20110412-1532.

OK, thank you.

Comment 17 Felipe Heidrich 2011-04-19 09:43:54 EDT

(In reply to comment #16)
> OK, thank you.

Try with a nightly build. Thank you.

Comment 18 Felipe Heidrich 2011-04-19 09:45:53 EDT

(In reply to comment #17)
> (In reply to comment #16)
> > OK, thank you.
> Try with a nightly build. Thank you.

avoid N20110418-2000 (Bug 343239)

Comment 19 Kentaroh Noji 2011-04-25 01:44:36 EDT

Verified the fix with the I-build as follows. 

- Version: 3.7.0, Build id: I20110419-1004
- Version: 4.1.0, Build id: I20110422-0200

The both builds work fine. Thank you!