Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CSourceNotFoundEditor


That sounds like a nice usability enhancement. I did the original work on
the CSourceNotFoundEditor but I didn't think of that scenario.

Let me know if I can help.

Thanks - Ken

> From: ext John Cortell <john.cortell@xxxxxxxxxxxxx>
> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
> Date: Thu, 21 May 2009 23:31:14 +0200
> To: "cdt-dev@xxxxxxxxxxx" <cdt-dev@xxxxxxxxxxx>
> Subject: [cdt-dev] CSourceNotFoundEditor
> 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

Back to the top