Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] DSF/CDI Launchers weirdness

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Alena Laskavaia
> Sent: Monday, April 12, 2010 12:28 PM
> To: CDT General developers list.
> Subject: [cdt-dev] DSF/CDI Launchers weirdness
> I was playing a bit with debugger lately and work flow is 
> really awkward for me.
> I don't have official build I am running from the trunk but 
> what I see is weird.
> So looks like DSF does not have a "Launcher" (the stuff you switch
> using link in the bottom) for Run
> configuration, but does for Debug. So I have to pick 
> different ones for Run
> and Debug. So I compile my app and do Run As->Local C++ App - 
> and it gives
> me list which does not include DFS - so I pick standard. When I debug
> I have to do it again to switch to DSF. If I do opposite - 
> pick DFS from Debug -
> when I do Run - my launch for run - does not do anything, cannot be
> terminated and
> deleted, and if I open launch configuration it shows that I use DSF -
> which is not in the
> list if I click on link.
> Is it expected behaviour?

We never used the DSF launcher for Run, we always used debug.  Run
was left to use the old one.  But I didn't know it caused the problem
above.  That is probably part of 6.0.  We have to fix that.


Back to the top