debugger: The DebuggerEngine refactoring.

This replaces the (de facto) singleton engines and data handlers by classes
that are instantiated per run. The DebuggerRunControl will now create an
object of (a class derived from) DebuggerEngine that contains all the relevant
"dynamic" data.

DebuggerManager is no more. The "singleton" bits are merged into DebuggerPlugin,
whereas the data bits went to DebuggerEngine.

There is no formal notion of a "current" DebuggerEngine. However, as there's
only one DebuggerEngine at a time that has its data models connected to the
view, there's still some "de facto" notion of a "current" engine. Calling
SomeModel::setData(int role, QVariant data) with custom role is used as the
primary dispatch mechanism from the views to the "current" data models
(and the engine, as all data models know their engine).

1 files changed, 3 insertions, 2 deletions

diff --git a/src/plugins/debugger/cdb/cdboptionspage.cpp b/src/plugins/debugger/cdb/cdboptionspage.cpp
index 4804a242ae..93f068b529 100644
--- a/src/plugins/debugger/cdb/cdboptionspage.cpp
+++ b/src/plugins/debugger/cdb/cdboptionspage.cpp
@@ -138,9 +138,10 @@ QString CdbOptionsPageWidget::searchKeywords() const
 }
 
 // ---------- CdbOptionsPage
-CdbOptionsPage::CdbOptionsPage(const QSharedPointer<CdbOptions> &options) :
-        m_options(options)
+CdbOptionsPage::CdbOptionsPage() :
+        m_options(new CdbOptions)
 {
+    m_options->fromSettings(Core::ICore::instance()->settings());
 }
 
 CdbOptionsPage::~CdbOptionsPage()