[Moose-dev] Re: verveinej out of memory

Yes, this is a feature The "--" serves as a separator between the arguments you want to pass to the JVM (before --) and the arguments you want to pass to the parser (after --) For example to use a specific class path for the JVM (maybe to use a different FAMIX implementation that the one provided) and to specify a class path for verveineJ where to look for things used in the source code, you can do: verveinej.sh -cp <class-path-for-the-JVM> -- -cp <class-path-for-verveinej> <source directory(ies)> nicolas De: "Matthias Junker" &lt;junker.matt(a)gmail.com&gt; À: "Moose-related development" &lt;moose-dev(a)iam.unibe.ch&gt; Envoyé: Jeudi 28 Avril 2011 23:07:53 Objet: [Moose-dev] Re: verveinej out of memory Hey, i just realized that executing the script without having the "--" in the command ignores the JOPTs argument. If you execute it like this: ./verveinej.sh -Xmx2000m PATH_TO_SILVERPEAS the "-Xmx2000m" is ignored. if you execute it like this it works: ./verveinej.sh -Xmx2000m -- PATH_TO_SILVERPEAS Cheers Matt On Tue, Apr 26, 2011 at 8:28 AM, Nicolas Anquetil &lt;nicolas.anquetil(a)inria.fr&gt; wrote: just when I was going to say that it is working and I corrected the bug you had when parsing ArgoUML :-( (it takes 1 hour to parse it all :-( Something I will have to look into without taking too much memory) Memory is indeed a problem currently and unfortunately there is not much I can do, since a lot of it is used by JDT's parser. There are few possible solutions: - there is a limit to the max. memory the JVM can use, but on my computer iti is at least 2500m. You specified only 2000m, so there is a possibility that the extra 500m will be enough... - incremental parsing: VerveineJ generates an output.mse file. When it starts, it check if such a file already exist. If so, it loads it in memory (silently, this is not a good idea) and new entities will be added to the existing ones. so you can call it several time with various parts of the project to parse. If the classpath is correctly specified, it should be able to do the name resolution correctly. (I am not sure how much this can improve things ...) - I could start to implement options reducing the level of detail of the output: --noFileAnchor, --noInvocation, --noLocalVariable, ... ? If it is an option in this case, it would help. - finally, if all else fails, there is always Markus' theory that they will always build newer, faster, bigger, computers. In 18 months, we will have twice as much memory to run verveineJ ... nicolas PS: I will try your test case ASAP (but it might be difficult this week) ----- Mail original ----- _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev