Community
Participate
Working Groups
OS: RHEL 4.0 update 2 Build level: I20050915-0800 JDK version: IBM JDK 1.4.2 SR2 Test case #: 4.05 CREATING A PLUG-IN WITH A PROPERTY PAGE Summary: G2X: Dump occurs while running 'Plug-in with a property page' Steps to recreate problem: 1. Select File -> New -> Project -> Plug-In Project in the Eclipse workbench 2. Enter a project name and click Next 3. Accept the default values in 'Plug-in Content' and click Next 4. Select 'Plug-in with a property page' and click Next 5. Accept the default values in the 'Sample Property Page' and click Finish 6. Select Run -> Run As -> Eclipse Application 7. A new workbench is launched 8. In the new workbench, create a project and a file named *.* (ex: abc.def) and perform some actions (ex: create files, review the Properties of the files... etc) Error: 1. The new workbench usually hangs while create a file at step 8 2. In the Console view of the original workbench, a message is displayed as 'JVMDG217: Dump Handler is Processing Signal 11 - Please Wait.' Expected Result: The plug-in should run with no problems.
Created attachment 27380 [details] Dump msg is displayed in the original workbench
Not a PDE issue. The problem appears to occur when a new file is created, which has nothing to do with the plug-in PDE generated.
Signal 11 is a segmentation fault, which means the VM will crash. When this occurs, there should be a crash log from the VM in whatever was the current directory of the Java process (probably wherever you ran the hosting eclipse from). Can you please post the crash log?
I reproduced this problem, but didn't find any crash log in the system.
This sounds like a VM crash. Are you running the J9 VM? Are you running in English locale or another language (I noticed G2X in the bug's title)? Any crash log(s) that are generated are likely in the /eclipse directory where the version of Eclipse you ran is installed.
A couple more things to try: 1. Can you replicate this using a RedHat 3.0 machine - 4.0 is not an official supported platform for Eclipse 3.1. http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html#TargetO peratingEnvironments 2. Can you replicate this using a Sun 1.4.2 VM?
Note that the bug was reported against I20050915-0800 and RHEL 4 is a target for 3.2 (but 3.1 should work without VM crashes too, of course) :)
We were able to replicate with ibm jdk 1.4.2 SR2. Could not replicate when using Sun 1.4.2 vm. Now we need to run it against J9.
I can't reproduce on my box using a J9 VM.
Karice: When you reproduced, did you get a VM crash log?
no crash log was written.
Tiffany, if you could still try to replicate this using a Sun 1.4.2 VM and the J9 VM (if you can get access to it) that would be helpful. Also, if you could provide the exact build id by running the java vm with the -version argument and provide that info in the bug report that would be great, too. Thanks.
1. We don't have RHEL 3.0 environment, we can't try this problem on RHEL 3.0. 2. I re-tested it with Sun 1.4.2 JDK, this problem doesn't exist. The version of Sun 1.4.2 is: java version "1.4.2_09" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05) Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode) 3. I tried to launch eclipse by './eclipse -clean -vmargs -xj9' or './eclipse' with IBM 1.4.2 JDK, the problem occurs. The version of IBM 1.4.2 is: java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20050609 (JIT enabled: jitc))
To launch the J9 vm you need to use command line argument -Xj9. I'm pretty sure it's case sensitive on the X, using -xj9 will not launch the J9 vm. I will be logging a bug against the IBM JDK for this.
Sorry. It's a typo in comment #13. I used the command './eclipse -clean -vmargs -Xj9' with IBM 1.4.2 JDK. And The problem still exist.
Tiffany - are you sure you ran the J9 VM and were able to replicate the problem - the VM version in comment #13 is not a J9 VM version. We had someone try the steps using the following J9 VM and could not replicate. java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 2.2) IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux x86-32 j9xia32142-20050609 (JIT enabled) J9VM - 20050524_1738_lHdSMR JIT - r7_level20050518_1803) However, we had someone else replicate the problem using the same (non-J9) VM you were using: java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20050609 (JIT enabled: jitc))
VM bug logged. 93921,001,866
Hi Karice, We use the JDK downloaded from IES download. (http://ies.ottawa.ibm.com/ies/downloads/index.php) The filename is "ibm-java2- ws-sdk-pj9n142-20050609.zip". I thought that it was a J9 version. Besides, I also try to find another JVM from JIT. The JVM with J9 is the same with the one we downloaded from IES. Is there any other JVM with J9 available? Thanks. Regards, Jacqueline
Ok, that filename looks like it has J9. I think when you run java -version to get the J9 version you have to run java -Xj9 -version to get the J9 vm version. But it's ok. We were able to replicate here using the same vm (non- J9). The name of the zip was something I didn't have though - thanks.
Hi Karice, Is this a problem of vm or we still need more investigation? The status is updated to "RESOLVED". If this is a vm problem, are we expected to close this bug before the vm is fixed? If this might be a bug of eclipse, we would like to re-open it. Please let us know the result of investigation. Thank You!! Regards, Jacqueline
See comment #17
Created attachment 27887 [details] stack of the IBM JVM This is a stack dump of the IBM JVM process (non-J9) after starting eclipse and creating a new file (before even trying to open the properties page). It prints out: JVMDG217: Dump Handler is Processing Signal 11 - Please Wait. and then hangs, taking 50% of the CPU Red Hat Enterprise Linux WS release 4 (Nahant Update 1) kernel 2.6.9-11.EL java -version java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20050609 (JIT enabled: jitc)) PW
Since this is a bug of JVM and the problem has been reported, we close this bug. Thanks!
