Community
Participate
Working Groups
R3.2.2 build 20061220 When I start my workspace in 3.2.2 I am getting a core dump (I will attach the whole thing). The only active Thread in my stack has this trace 3XMTHREADINFO "Worker-6" (TID:0x16908600, sys_thread_t:0x12C0F400, state:CW, native ID:0x0000094C) prio=5 4XESTACKTRACE at org/eclipse/jdt/internal/compiler/classfmt/ClassFileReader.initialize(ClassFileReader.java:877) 4XESTACKTRACE at org/eclipse/jdt/internal/compiler/classfmt/ClassFileReader.<init>(ClassFileReader.java:324(Compiled Code)) 4XESTACKTRACE at org/eclipse/jdt/internal/core/ClassFile.getJarBinaryTypeInfo(ClassFile.java:296) 4XESTACKTRACE at org/eclipse/jdt/internal/core/ClassFile.existsUsingJarTypeCache(ClassFile.java:197) 4XESTACKTRACE at org/eclipse/jdt/internal/core/NameLookup.seekTypesInBinaryPackage(NameLookup.java:957) 4XESTACKTRACE at org/eclipse/jdt/internal/core/NameLookup.seekTypes(NameLookup.java:932) 4XESTACKTRACE at org/eclipse/jdt/internal/core/NameLookup.findType(NameLookup.java:729) 4XESTACKTRACE at org/eclipse/jdt/internal/core/NameLookup.findType(NameLookup.java:613) 4XESTACKTRACE at org/eclipse/jdt/internal/core/NameLookup.findType(NameLookup.java:767) 4XESTACKTRACE at org/eclipse/jdt/internal/core/JavaProject.findType(JavaProject.java:1199) 4XESTACKTRACE at org/eclipse/jdt/internal/core/JavaProject.findType(JavaProject.java:1186) 4XESTACKTRACE at org/eclipse/jdt/internal/core/JavaProject.findType(JavaProject.java:1173) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ExtensionsErrorReporter.validateJavaAttribute(ExtensionsErrorReporter.java:483) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ExtensionsErrorReporter.validateExtensionAttribute(ExtensionsErrorReporter.java:283) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ExtensionsErrorReporter.validateExistingExtensionAttributes(ExtensionsErrorReporter.java:269) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ExtensionsErrorReporter.validateElement(ExtensionsErrorReporter.java:175) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ExtensionsErrorReporter.validateElement(ExtensionsErrorReporter.java:188) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ExtensionsErrorReporter.validateExtension(ExtensionsErrorReporter.java:138) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ExtensionsErrorReporter.validateContent(ExtensionsErrorReporter.java:105) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ManifestConsistencyChecker.checkFile(ManifestConsistencyChecker.java:94) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ManifestConsistencyChecker.checkThisProject(ManifestConsistencyChecker.java:51) 4XESTACKTRACE at org/eclipse/pde/internal/core/builders/ManifestConsistencyChecker.build(ManifestConsistencyChecker.java:40) 4XESTACKTRACE at org/eclipse/core/internal/events/BuildManager$2.run(BuildManager.java:603) 4XESTACKTRACE at org/eclipse/core/runtime/SafeRunner.run(SafeRunner.java:37(Compiled Code)) 4XESTACKTRACE at org/eclipse/core/internal/events/BuildManager.basicBuild(BuildManager.java:167) 4XESTACKTRACE at org/eclipse/core/internal/events/BuildManager.basicBuild(BuildManager.java:201) 4XESTACKTRACE at org/eclipse/core/internal/events/BuildManager$1.run(BuildManager.java:230) 4XESTACKTRACE at org/eclipse/core/runtime/SafeRunner.run(SafeRunner.java:37(Compiled Code)) 4XESTACKTRACE at org/eclipse/core/internal/events/BuildManager.basicBuild(BuildManager.java:233) 4XESTACKTRACE at org/eclipse/core/internal/events/BuildManager.basicBuildLoop(BuildManager.java:252) 4XESTACKTRACE at org/eclipse/core/internal/events/BuildManager.build(BuildManager.java:285) 4XESTACKTRACE at org/eclipse/core/internal/events/AutoBuildJob.doBuild(AutoBuildJob.java:154) 4XESTACKTRACE at org/eclipse/core/internal/events/AutoBuildJob.run(AutoBuildJob.java:217) 4XESTACKTRACE at org/eclipse/core/internal/jobs/Worker.run(Worker.java:58)
Created attachment 56345 [details] Full java core
Note that the second time I started it was fine
Look like a VM issue.
Assigning to Frédéric since he is the only one in the team with a Vista box.
I never got such a problem while running vista neither with 3.3 nor with 3.2 using Sun's VM... So, I guess this problem needs to be reported to VM team...
