So I did a bunch more testing, and this is what I found: - The IntelliJ debugger ignores the “source” declaration in the class file and instead always looks for a “.java” file in the source path - The file must contain a java class declaration with the same name - The file must be “recognized” by IntelliJ before the debugger stops, so you can’t dynamically generate a bogus java file - If the file is not present, the debugger will not show local variables - The debugger seems to ignore local variable type declarations, so the “Evaluate Expressions” window does not get type ahead (but works otherwise).
I might try adding a JSR-45 SMAP, but I don’t have high hopes based on Charlie’s comments at the last summit. Does anyone else have any ideas on things that might work? -dain On Apr 1, 2015, at 11:08 PM, Dain Sundstrom <d...@iq80.com> wrote: > Hi all, > > I think this might have been asked before... Has anyone gotten the intelliJ > debugger to step through the source file for their language? > > Adding the source and line numbers during generation makes stack traces to > come out correctly, and Intellij even opens the correct file location. > During debugging, I can see the correct correct source and line numbers, but > intellij doesn’t open the file. > > I’d even be ok with a hacky solution where I rename all of my files to be > “x.java”. > > Thanks, > > -dain _______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
