+1
As far as DSF-GDB, I think it's also worthwhile to make sure that you
can install DSF-GDB and CDI-GDB separately, which is the case now.
Eventually, I would also like to see CDI be separated from rest of CDT,
but perhaps that's just my preference for neatness.
Cheers,
Pawel
Doug Schaefer wrote:
I guess from my angle, DSF/GDB is fairly separate from DSF
proper. I think we need to keep open the opportunity to push DSF down
into the debug platform, especially as more debuggers are built on it.
For example, I plan on spending a little time to see if putting Java
debugging on DSF would help with JNI debugging. But that is separate
from the GDB support, which probably should be allowed to be CDT
specific. And for Nokia's debugger, it's really whatever you want to do
with it.
Just my thoughts...
Doug.
On Fri, Sep 11, 2009 at 1:49 PM, <Ling.5.Wang@xxxxxxxxx>
wrote:
Hi,
Pawel and Marc,
I remember DSF was originally design with one intension of not being
dependent on CDT, thus DSF launch delegates are not derived from
AbstractCLaunchDelegate, and DSF/GDB has its own copies of launch
config tabs (such as CMainTab and DebuggerTab) instead of deriving from
those in CDT.
Now as DSF being moved into CDT, I'm wondering if we still want to keep
the independency ? Or is it better we consolidate those code ? For
instance we in Nokia added a feature in CDT and now we have to kind
of copy the code to EDC (the new DSF based debugger) unless we change
the LaunchDelegate inheritance tree.
Thanks.
- Ling_______________________________________________
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
|