Bug 336386

Description Dobrin Alexiev 2011-02-04 13:44:40 EST

Build Identifier: CDT 8

I wanted to add a project to my global source Lookup.
In the preference page:  “C/C++ -> Debug -> Source Lookup Path” I clicked on the “Add” button. 
In the “Add Source” dialog I selected the “project” item and clicked “OK”. 
A new dialog “Referenced Project” popped up asking me about referenced project. 
When I click “OK” a new item called “Project” appeared in my “Source Lookup Path” preference page, but I was never asked to specify the project !!!
If I select the “project” item the Edit button in the page is disabled. 
 
Is there something I am missing. 
This used to work well – I was able to specify the project in the past. 
 
Thanks
Dobrin


Reproducible: Always

Steps to Reproduce:
Here is the initial discussion in the CDT mailing list: 

I read through bug 225805 https://bugs.eclipse.org/bugs/show_bug.cgi?id=225805#c20
I looks to me that there are some scalability/performance issues with the GDB debugger integration with Eclipse if projects with big trees are being set as source lookup containers. 
If GDB  is the only CDT debugger it looks like a reasonable solution to cut or augment a feature introduced earlier to save trouble to many customers. 

The problem is that for other CDT debuggers having the “Project” container the old way is a good use case with no performance issue for an average size project. 
I wander if other people was surprised by changing the meaning of “Project” containers? 
Or many be the change is too recent, so not too many customers have seen it? 

Anyway, 
Is it possible to have the “Project” container the old way, and introduce a new container that works in the new “project” way?

This way: 
When a GDB debug sessions starts it can advise the users that there may be scalability problems with the old “Project” containers any suggest the user to use the new ones? 
The customers of our debugger won’t be upset that a feature they are used to is missing in the next version.

Thanks
Dobrin


From: cdt-dev-bounces@eclipse.org [mailto:cdt-dev-bounces@eclipse.org] On Behalf Of Sergey Prigogin
Sent: Thursday, February 03, 2011 5:25 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] global source lookup

It still looks like the right way to deal with the use cases you described is to use dependent projects and to enable ""Add projects referenced by the target project".  Global source lookups that were configured with references to specific projects will continue to work, but the new UI doesn't allow users to add new named project containers to the global lookup. I'd be glad to extend the UI to allow adding named projects to the global source lookup, if you can figure out how express the distinction between explicitly named and target project source containers in a way that won't confuse the hell out of all users.

-sergey
On Thu, Feb 3, 2011 at 2:10 PM, Alexiev, Dobrin <dalexiev@ti.com> wrote:
The project field in our launch configurations is optional. 
Very often the users load the OUT file from the file system and they don’t specify any project in their launch configuration. 
 
Often the OUT files were build in with relative source info, but that is not always the case. 
When the information in the OUT file is not complete users create projects that are just containers for the source files for these OUT files. 
So in that case any launch configuration they create needs to use the “source file container” projects as part of its source lookup. 
 
Dobrin
 
From: cdt-dev-bounces@eclipse.org [mailto:cdt-dev-bounces@eclipse.org] On Behalf Of Sergey Prigogin
Sent: Thursday, February 03, 2011 3:21 PM

To: CDT General developers list.
Subject: Re: [cdt-dev] global source lookup
 
 
On Thu, Feb 3, 2011 at 11:47 AM, Alexiev, Dobrin <dalexiev@ti.com> wrote:
The use case is: 
 
The user is loading multiple libraries/modules/DLLs  in their programs.
Each launch configurations is setup to load different program but the DLLs the programs loads is frequently the same between programs. 
In that case the user has to specify in each launch configuration the path to the projects containing the source files for each of the DLL.
 
Wouldn't all DLL projects be dependencies of any project that builds an executable in that use case? Would enabling "Add projects referenced by the target project" be sufficient to cover this use case?
 
-sergey
 
A preferable solution is to specify the projects with the commons DLLs source once and each of the launch configurations will be able to find the source file with no additional setup.
 
Isn’t this the reason we have Default Source Lookup? 
All other containers added to the preference page work the same way, right? 
They are shared between all launches. 
 
I understand the need for much smarter source lookup that simple Project containers…
But that doesn’t mean we should remove the feature that is being used and working. 
 
Thanks
Dobrin
 
From: cdt-dev-bounces@eclipse.org [mailto:cdt-dev-bounces@eclipse.org] On Behalf Of Sergey Prigogin
Sent: Thursday, February 03, 2011 2:28 PM

To: CDT General developers list.
Subject: Re: [cdt-dev] global source lookup
 
Please take a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=225805#c20 for the reasoning behind the change. Target project source lookup is no longer the only option for the default lookup. As a side effect of my change, it's no longer possible to add specific projects to the global source lookup. We can try to change it back, but before we do that I would like to understand the use case. Using specific project names in the global preferences looks like a bad practice to me.
 
-sergey
 
On Thu, Feb 3, 2011 at 11:03 AM, Alexiev, Dobrin <dalexiev@ti.com> wrote:
Sergey,
Can you explain a bit more…
 
>>>> Why would you need a specific project in the global settings?
I want to specify set of projects that will be used for source lookup for all my launch configurations. 
CDT used to work that way.  Why is that changed?
 
I am not sure I understand what you mean by: 
>>>> The project that gets added in the global settings is the one that the launch configuration is attached to
It make sense the project that I specific  in the main tab of my launch configuration to be used as part for source lookup. 
Why would I need to add it to the global preference? How will that make a difference if I add a project or I don’t add a project container to the global preference? 
I’m pretty puzzled…
 
Thanks
Dobrin
 
From: cdt-dev-bounces@eclipse.org [mailto:cdt-dev-bounces@eclipse.org] On Behalf Of Sergey Prigogin
Sent: Thursday, February 03, 2011 1:52 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] global source lookup
 
The project that gets added in the global settings is the one that the launch configuration is attached to. Why would you need a specific project in the global settings?
 
-sergey
On Thu, Feb 3, 2011 at 10:43 AM, Alexiev, Dobrin <dalexiev@ti.com> wrote:
Hello, 
 
I wanted to add a project to my global source Lookup.
In the preference page:  “C/C++ -> Debug -> Source Lookup Path” I clicked on the “Add” button. 
In the “Add Source” dialog I selected the “project” item and clicked “OK”. 
A new dialog “Referenced Project” popped up asking me about referenced project. 
When I click “OK” a new item called “Project” appeared in my “Source Lookup Path” preference page, but I was never asked to specify the project !!!
If I select the “project” item the Edit button in the page is disabled. 
 
Is there something I am missing. 
This used to work well – I was able to specify the project in the past. 
 
Thanks
Dobrin
 
 
 
 

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

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

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

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