Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] module specific source lookup

The preference page "C/C++, Debug, Common Source Lookup Path" is contributed by "org.eclipse.cdt.debug.ui" via the class SourcePreferencePage. 

That class is using the object returned by CDebugCorePlugin.getDefault().getCommonSourceLookupDirector().

I don't see how I can override it. 

Also, if two debugger plugins are adding different source containers shouldn't they all be visible in the same preference page? 

It works well in the Launch configuration dialog, but not in the preference page...

May be I am missing something...

Thanks
Dobrin

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
Sent: Thursday, June 04, 2009 4:01 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] module specific source lookup

An extension point seems like an overkill to me.  Shouldn't sub-classing 
be enough?

Cheers,
Pawel

Alexiev, Dobrin wrote:
> I created my own source lookup container type. 
>
> It worked well with the exception that it won't appear in the user preference dialog "Add Source" under the preference page "C/C++, Debug, Common Source Lookup Path". 
>
> It does appear in my launch configuration dialog since my launch has its own source lookup director derived from CSourceLookupDirector. 
>
> I noticed that CSourceLookupDirector class has in a list all container types he understands. 
>
> Should there be an extension point so the C source director allows adding other container types in its preference page? 
>
> I can create a patch that will allow that. 
>
> Or there is other way to achieve this....
>
> Thanks
> Dobrin
>
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mikhail Khodjaiants
> Sent: Friday, May 29, 2009 12:30 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] module specific source lookup
>
> Dobrin,
>
> Would it work if you simply define add a new "module" source container
> type? You can add path mappings as child containers to it.
>
> Mikhail  
>
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Alexiev, Dobrin
> Sent: Friday, May 29, 2009 5:20 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] module specific source lookup
>
> Hello, 
>
> I am in the process of integrating our backend debugger in Eclipse using
> the DSF framework. Here is one use case I need to satisfy. 
>
> The user is debugging a program that has multiple modules (DLLs, shared
> objects). Each of the modules (DLLs, shared objects) is compiled
> separately - the source files for that module are in their own directory
> structure. 
>
> Most importantly - the names of the source files compiled into different
> modules can be the same but they really are different files. For example
> "main.c" can appear in many modules. 
>
> The user suspends the program. The Debug View shows stack frames from
> different modules. Some of the frames point to a source files with the
> same name - "main.c" but different module. 
>
> The debugger will properly identify which "main.c" is from which
> directory structure because the module name plus the source file name
> will uniquely identify the location of the source file. 
>
> In some cases the OUT file can be moved away from the location it was
> built. In these cases the user will be prompted to specify the path to
> one of the source files for that module. The rest of the source files
> will be found automatically. The information the user entered will be
> specific for that module and won't be used to perform source lookup for
> other modules. 
>
> I think the main idea here is: A soruce location is based not only on
> source file name but also on module name. That will provide more
> accurate information to perform source lookup. 
>
> If other people think this approach for source lookup makes sense and
> will benefit other users, I could open a Bugzilla entry and further
> discuss the requirements, design and implementation for this use case. 
>
> Thanks
> Dobrin
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>   

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev



Back to the top