Hi andrea,
I see you found a solution o your problem (thanks to Jannik)
On the side of VerveineJ, another solution is to use incremental parsing. You can parse the project in small parts (ultimately you could parse it one file after the other). As long as you specify the correct class path to verveinej and don't touch the mse file generated, it should work.
nicolas
On 02/08/12 07:22, Andrea Caracciolo wrote:
Hi,
I' trying to run verveineJ on the Eclipse source code .. and i always get this:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space at java.util.LinkedList.addBefore(LinkedList.java:778) at java.util.LinkedList.add(LinkedList.java:198) at fr.inria.verveine.core.Dictionary.getEntityByName(Unknown Source) at fr.inria.verveine.extractor.java.JavaDictionary.ensureFamixMethod(Unknown Source) at fr.inria.verveine.extractor.java.VerveineVisitor.visitVariablesDeclarations(Unknown Source) at fr.inria.verveine.extractor.java.VerveineVisitor.visit(Unknown Source) at org.eclipse.jdt.core.dom.FieldDeclaration.accept0(FieldDeclaration.java:279) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:219) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at fr.inria.verveine.extractor.java.FamixRequestor.acceptAST(Unknown Source) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:1016) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:628) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:988) at fr.inria.verveine.extractor.java.VerveineJParser.parse(Unknown Source) at fr.inria.verveine.extractor.java.VerveineJParser.main(Unknown Source)
I tried adding -Xmx4000m .. but i still get the same exception.
Is there another trick ?
Thanks. Andrea _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev