Re: [cdt-dev] CSourceNotFoundEditor

[John Cortell <john.cortell@xxxxxxxxxxxxx>]

The "locate file" updated the source lookup for the launch 
configuration, too. The issue is that it only updates only one 
(active) launch configuration. There could be 10 launch 
configurations for the same executable. All 10 should be updated.

John

At 08:48 AM 5/22/2009, Elena Laskavaia wrote:
> I though editor has 3 buttons and second if something like 
> "configure source lookup" and it does edit source lookup for launch 
> configuration,
> is it not enough?
>
> John Cortell wrote:
> > When the user steps into a function during a debug session, and the 
> > file containing that function can't be found, a mostly-empty editor 
> > is shown. It contains a button that allows the user to "locate" the 
> > file. So that the file can be found again in future debug session, 
> > CDT adds a path mapping to the launch configuration which spawned 
> > the debug session. This is very useful.
> > However it could do better. Say the user terminates that debug 
> > session, and invokes another launch configuration which debugs the 
> > same executable. He steps into that same function. He gets the 
> > special editor again that asks him to locate the file. He grunts; 
> > he just spent 20 seconds telling the debugger where it is. Did it 
> > forget already? This scenario is common in multicore.
> > What I'm thinking of doing is enhancing the logic in 
> > CSourceNotFoundEditor to have it add the mapping to all launch 
> > configurations which reference the executable being debugged. I'm 
> > polling to see whether this is behavior the community wants. If so, 
> > I'll contribute it.
> > John
> >
> > _______________________________________________
> > 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