Debugging Graal-enabled OpenJDK

[Tom Rodriguez]

> On Oct 3, 2016, at 10:55 AM, Andrew Haley <aph at redhat.com> wrote:
> 
> On 03/10/16 18:18, Tom Rodriguez wrote:
>> 
>>> On Oct 3, 2016, at 10:12 AM, Andrew Haley <aph at redhat.com> wrote:
>>> 
>>> So I'm now seeing Graal classes loaded -- lots of them -- but I can't
>>> set a breakpoint on any of them.  I'm using the Eclipse configuration
>>> but whenever I try to Navigate > Open Type > I can't see any Graal
>>> classes.  I can see the standard Java library classes, but not the
>>> Graal ones.  I want to step through compilation.
>> 
>> I assume you built this yourself?
> 
> Yes.
> 
>> Are running with the eclipse project files produced by “mx eclipseinit”?  That should let you debug Graal.  I’ve never tried debugging it without that.
> 
> Well, I think I am, but I confess my knowledge of Eclipse is limited.
> I tried to load the project files into Eclipse, but I don't know if
> that worked.  The instructions about how you load a project file
> into Eclipse are not at all specific.

Yes, it does assume some eclipse experience.  If you have about 150 project loaded then you’ve got all loaded properly.  There shouldn’t be any error messages in the log or on the projects either.  And you’re following the instructions here https://github.com/graalvm/graal-core/blob/master/docs/Debugging.md#ide-support?  The loading of the debug configuration takes care of pointing eclipse at all the sources.

I’d also recommend setting the preference for Launch Operation in Run/Debug -> Launching to “Always launch the previously launched application.”  This will make it always try to do the attach instead of being smart.  I’m going to add that to the debugging notes.

tom

> 
> Andrew.
> 
>