RE: [cdt-dev] Renaming "DSF Disassembly"
From a quick look, there is no technical reasons to have
these things in the gdb plugins.
DSF being a framework, I usually add new features to
DSF-GDB and once they are proved stable,
we move them to DSF. That is why I put those features
But since there is an important reason to have them in DSF,
it would be very easy to move them.
I just noticed that I can't set breakpoints or run to line,
etc since I don't have any gnu plugins. Anxious to hear the reasoning for
those being gdb specific.
The toggle breakpoints support being GDB specific I (now)
understand, but not the line actions. Maybe Marc can shed some light on why
that stuff is housed there.
At 10:18 AM 2/19/2010, Madan
For viewer to work with CDI there're the following
1. /org.eclipse.cdt.dsf.ui - the actual DSF viewer and its
dependencies org.eclipse.cdt.dsf, org.eclipse.cdt.dsf.gdb
org.eclipse.cdt.dsf.gdb.ui - for IToggleBreakpointsTargetExtension and
IMoveToLineTarget/ IResumeAtLineTarget / IRunToLineTarget
From: cdt-dev-bounces@xxxxxxxxxxx [
mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of
Sent: Friday, February 19, 2010 6:06
Subject: RE: [cdt-dev]
Renaming "DSF Disassembly"
Given the view is still in DSF,
why would we move the prefs out of the DSP plugin?
Well, if it's shared between DSF and CDI, then it's
really not a DSF feature and I would assume it would be in
org.eclipse.cdt.debug.ui. Is DSF required in CDT 7.0 or can vendors
ship without it if they're only using CDI?