forked from qt-creator/qt-creator
Debugger: Identify a breakpoint's requested parameters with preset data
This removes the ability to have different enabled/disabled states for the same breakpoint in concurrently running engines, but make the behavior less surprising. At least currently people *do* expect breakpoint changes in a running engine to persist after the engine dies. Change-Id: I911594765b24f2ce58f6747ae5ecab3e608882b8 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This commit is contained in:
@@ -205,11 +205,11 @@ private:
|
||||
void setState(BreakpointState state);
|
||||
|
||||
const GlobalBreakpoint m_globalBreakpoint; // Origin, or null for aliens.
|
||||
BreakpointParameters m_requestedParameters; // May differ from global value over lifetime of breakpoint.
|
||||
BreakpointParameters m_parameters;
|
||||
BreakpointParameters m_parameters; // Parameters acknowledged by engine.
|
||||
BreakpointParameters m_alienParameters; // Requested parameters in case of no associated global bp.
|
||||
BreakpointState m_state = BreakpointNew; // Current state of breakpoint.
|
||||
BreakpointMarker *m_marker = nullptr;
|
||||
QString m_responseId; //!< Breakpoint number or id assigne by or used in the debugger backend.
|
||||
QString m_responseId; //!< Breakpoint number or id assigned by or used in the debugger backend.
|
||||
QString m_displayName;
|
||||
};
|
||||
|
||||
|
||||
Reference in New Issue
Block a user