forked from qt-creator/qt-creator
6a6cba5518
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).
Thinks to check: - loading of custom dumpers (as seen on QByteArray/QString) - availability of Qt debug information (custom display of QObject derived class) - availabitily of Qt sources (single step into some Qt *._cpp_ file) - setting of breakpoints on dynamically loaded plugins (try plugin.cpp here, especially in constructors) - check I/O (qDebug, std::cout, std::cerr)