Debugger: Use kit macro expander instead of global one where possible

This is low hanging fruit enabling a lot more customization.

Change-Id: I1a90fa731ea512852c12a55fad75551efb44e875
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
This commit is contained in:
hjk
2016-03-22 10:47:03 +01:00
parent 3c2f0096ea
commit d27d51050c
6 changed files with 23 additions and 6 deletions

View File

@@ -44,6 +44,7 @@ class QAbstractItemModel;
QT_END_NAMESPACE
namespace Core { class IOptionsPage; }
namespace Utils { class MacroExpander; }
namespace Debugger {
@@ -112,6 +113,8 @@ public:
bool nativeMixedEnabled = false;
Utils::MacroExpander *macroExpander = 0;
// For Debugger testing.
int testCase = 0;
};
@@ -319,6 +322,9 @@ public:
void updateBreakpointMarker(const Breakpoint &bp);
void removeBreakpointMarker(const Breakpoint &bp);
QString expand(const QString &string) const;
QByteArray expand(const QByteArray &string) const;
signals:
void stateChanged(Debugger::DebuggerState state);
// A new stack frame is on display including locals.