Subject: Re: Checking the Checker Plugin...
From: Edward P. Hom (ehom@ccs.neu.edu)
Date: Sun Dec 08 2002 - 16:23:18 EST
Paul,
Have you tried making a shortcut to Eclipse and specifying -vmargs?
the syntax is:
eclipse.exe [platform options] [-vmargs [JVM args]]
so, for instance, you might have:
eclipse.exe -vmargs -Xmx512M
to run Eclipse with maximum Java heap size of 512MB.
go here for more information:
http://www.eclipse.org/documentation/html/plugins/org.eclipse.platform.doc.user/doc/tasks/running_eclipse.htm
-Edward Hom
ehom@ccs.neu.edu
On Sun, 8 Dec 2002, Paul Freeman wrote:
> Hi Karl -
>
> Some of the students pointed out that there is no main method which the
> checker should start and stop around. I think I am able to modify the
> checker to work around this, but another issue came up when I tried to
> do this.
>
> I had mentioned in class that the AspectJ compiler had given me "out of
> memory" errors when I tried to compile a larger program with the checker
> attached. I get the same error when trying to compile the plugin with
> the checker attached. There is a setting in the batch file (and shell
> script for unix) that allows you to increase the memory allotted to the
> AspectJ compiler when it starts from the command line, but the Eclipse
> environment does not use either of those files to start the AJ compiler
> thread. In order to fix this there would need to be a similar file used
> to start Eclipse itself, and there does not appear to be. At least on
> my windows installation, Eclipse is started from an executable not a
> batch file.
>
> The other option would be to compile the plugin with the checker
> attached from the command prompt, but again due to the wonders of
> windows, that seems to be impossible due to the large number of
> libraries which are required to be attached to the classpath. On my
> machine I have not been able to create a compile statement which does
> not throw an "out of environment space" error due to the size of the
> classpath variable I am trying to pass as an argument. Even if this
> option did work, I think it might be a bit awkward to have the rest of
> the class perform without causing a lot of problems.
>
> Is there another smaller program that we might be able to be examined
> with the plugin? One that hopefully will not throw "out of memory
> errors" from Eclipse?
>
> Or perhaps there is another question that could be asked for that part
> of the final.
>
> Paul
>
>
This archive was generated by hypermail 2b28 : Sun Dec 08 2002 - 16:23:19 EST