Hey Matt, Unfortunately, it's not currently possible to specify arguments to the JVM that runs the GWT compile. We're aware of the demand for this feature though, so expect it in a future release.
As an absolute workaround, could you rename your java binary and create a shell script in its place that launches the real java binary with whichever args you want (prepended to the args given to the shell script)? jason On Fri, Apr 17, 2009 at 2:34 PM, Matt Mastracci <matt...@mastracci.com> wrote: > > I'm running into the same JVM crash under Eclipse that I was running > into from Ant a few weeks ago > (http://grack.com/blog/2009/04/14/gwt-16-crashes-and-a-fix/ > ) while trying to deploy a test AppEngine+GWT project. The output > from the compiler is pretty much: > > Compiling module ... > Invalid memory access of location 00000000 rip=01160767 > > Any ideas where the Eclipse Plugin gets the JVM and the JVM arguments > to run to GWT portion of the compile? I tried adding the JIT > overrides to the workspace JRE default JVM properties, but those don't > seem to get picked up. > > -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/ > DataTreeNode,forwardDeltaWith > -XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ > ParameterizedTypeBinding,<init> > -XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ > ParameterizedMethodBinding,<init> > > The only argument I can see in the process list is "-Xmx512m". > > Thoughts/ideas? > > Thanks, > Matt. > > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
