[platform-debug-dev] Re: [jdt-debug-dev] (no subject)

[Darin Wright <Darin_Wright@xxxxxxxxxx>]

Hello,

Source lookup is organized as follows. A source lookup director directs 
source lookup among a set of source lookup participants and a set of 
source containers. The containers are the the locations where source code 
is located, and are generic (i.e. search for source files based on name). 
The source lookup director and participants are the domain specific 
components. A source lookup director is associated with a type of launch 
configuration, and has the responsibility of contributing the initial 
source lookup participants involved in source lookup. However, there is 
more flexibility, as you can programatically contribute source lookup 
participants at a later time. Source lookup participants provide source 
file names for debug artifacts (stack frames) during source lookup (i.e. 
name translation).

There is one source lookup path that the user edits, per launch. The 
default path is provided by the source path computer associated with a 
launch config. All source lookup participants share the same source lookup 
path, but do not have to understand/use all of it.

We do not currently support multiple independant source lookup paths for a 
launch. We support a shared source lookup path with different participants 
(for cross language debugging).

Please enter a feature request if required. However, for 3.0, this will 
not be changing. 

Darin 




Shu Tan/Toronto/IBM@IBMCA 
Sent by: jdt-debug-dev-admin@xxxxxxxxxxx
06/07/2004 09:39 AM
Please respond to
jdt-debug-dev


To
platform-debug-dev@xxxxxxxxxxx
cc
jdt-debug-dev@xxxxxxxxxxx
Subject
[jdt-debug-dev] (no subject)











Hi,

In eclipse 3.0 M9,  It is nice that source lookup has been changed to more
frame oriented approach.   However, I have a question.

It seems that one launch has only one ISourceLookupDirector,  and
ISourceLookupDirector manages the many ISourceContainers,  is it possible
that ISourceLookupDirector
manages two or more different sets of ISourceContainers? and how to do
that?

Let's say that I have different stack frame under one thread or under
different debug target.  For each type of stack frame,  the source search
path is different, ( i.e  each
has a different set of SourceContainers. ).   it seems that
ISourceLookupDirector needs to identify them,  but does it handle it and
how?

Thanks,

Shu Tan








_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-debug-dev