[news.eclipse.technology.ldt] Re: JSR 45 and support for non-Java class

[Per Bothner <per@xxxxxxxxxxx>]

Darin Wright wrote:
> The Eclipse Java debugger does support JSR-45.

In a stack trace, I am getting the correct line number and local variables.
However, clicking on the stack trace entry, I get "Source not found" (and
an offer to Edit Source Lookup Path).

This happens even when File section of the SourceDebugExtension
includes the fully-qualied path:

Attribute "SourceDebugExtension", length:115
SMAP
strings.scm
Scheme
*S Scheme
*F
+ 1 strings.scm
/home/bothner/Kawa/work2/kawa/lib/strings.scm
*L
1#1,122:1
*E

One would also think that Eclipse should default to using the same paths
as for Java.  I.e. if class foo.bar has SourceFile "foo.scm" it should search
the same directories as it would search for "bar.java".

> In a similar scenario when testing with JSPs, the Java debugger will bring 
> up source for a JSP file. You have to be sure that the source lookup path 
> knows where to search for your source files.

I've tried editing the Source Lookup Path.  It currently shows:
> tmp
> lib - /home/bothner/Kawa/work2/kawa
> Default

The file strings.scm is in /home/bothner/Kawa/work2/kawa/lib.

Perhaps I should file a bug report.  Unfortunately, bundling up a reproducible
test case might be difficult.  I could tar up a directory.

Of course once we have stack trace -> source file working, the next goal
would be setting breakpoints in a Scheme source file.  Installing Dominique
Boucher's Scheme plugin (http://theschemeway.blogspot.com/) may be helpful
for that.
--
	--Per Bothner
per@xxxxxxxxxxx   http://per.bothner.com/