Community
Participate
Working Groups
RC 1 - JUnit setup - select Assert.assertEquals(String message, double expected, double actual, double delta) - activate cell editor for for row 0, column 0 - press enter. java version "1.4.1_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) GTK 2.2.1 No log files generated
Is there a java core file?
No I even didn't get a Java core file.
Felipe, another GTK 2.2.1 crash.
could you provide more details steps, like what do you mean by "JUnit setup". I've tried the Preference Page -> Java -> JUnit and could find any Assert.assertEquals(...) Thanks
See bug 32947 for an explanation. It contains also a zip file with the JUnit source code.
Not good enough Dirk. In the Bug#32947 you talk about "JUnit Project" and it's doesn't exits for me. What exists is a "Java Project" and they all have the same properties page regardless of their content. To open the properties page of a Java Project I select it, click with the right-button, and choose Properties in the pop-up menu. I wonder if you have a different plug-in that I don't have (Note: I have the org.junit plug-in). Note, Veronika and I have spent time on this and neither one can reproduce your scenario. Give us for info please.
OK, I can still reproduce it. Here are the steps: - start with a fresh workspace - create project JUnit - select JUnit - Import the zip file attached to bug 32947 using File->Import->Zip file - open class Assert from package junit.framework - select method Assert.assertEquals(String message, double expected, double actual, double delta) in outliner - activate Refactor->Change Method Signature - click on row 0, column 0 of the parameter table - press enter to activate the cell editor - press enter again observe: VM crashed.
Reproducible on GTK 2.2.1 Current Java thread: at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(Native Method) at org.eclipse.swt.widgets.Display.eventProc(Display.java:611) at org.eclipse.swt.internal.gtk.OS.gtk_main_iteration(Native Method) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1382) at org.eclipse.jface.window.Window.runEventLoop(Window.java:577) at org.eclipse.jface.window.Window.open(Window.java:557) at org.eclipse.jdt.internal.ui.refactoring.actions.RefactoringStarter.activate(RefactoringStarter.java:64) Btw, you don't need junit at all to reproduce this. The steps are: - select a method with at least one param on the outliner - activate Refactor->Change Method Signature - click on row 0, column 0 of the parameter table - press enter to activate the cell editor - press enter again crash
Approved for RC3 by Veronika.
Investigate for RC3.
Fix is very simple: remove the line OS.gtk_entry_set_activates_default (handle, true); from the createHandle of Text. In past we used to let the GTK do the default button behavior so this line used to be necessary. But not anymore. In the same scenario, change method signature dialog, we still have GTK bugs: 1 - The table cursor is behind table thefore invisible. 2 - When the text widget is dispose the focus goes to space... Anyhow, the bug report on this PR is fixed.
