GraalError

[Tom Rodriguez]

> On Oct 25, 2016, at 10:05 AM, Andrew Haley <aph at redhat.com> wrote:
> 
> On 25/10/16 18:03, Josef Eisl wrote:
>> If you are only interested in Graal compilations you could use
>> -Dgraal.PrintCompilation=true and/or -Dgraal.PrintAfterCompilation=true
>> which is in some cases more informative. Regarding the multiple the
>> threads printing at the same time issue, -XX:JVMCIThreads=1 might help.
> 
> More gems of information, thanks!  I'm glad all of this
> is going to the list.
> 
> Andrew.

-Dgraal.ExitVMOnException=true -Dgraal.DumpOnError=true are good options to use all the time during development.  DumpOnError should give you a copy of the LIR in the CFG file when the failure occurs.

You can also add force dumping at interesting points using DebugScope.forceDump.  That would usually either be a StructuredGraph or the LIR object.  You should have -Dgraal.DumpOnError=true on the command line too to enable the dumping machinery used by forceDump.

For debugging LIR problems try turning on -Dgraal.DetailedAsserts=true which I think dumps more extensive information about the problems with the LIR.

tom