2012-10-02 09:12:39 +02:00
|
|
|
/****************************************************************************
|
2010-05-07 15:16:31 +02:00
|
|
|
**
|
2016-01-15 14:57:40 +01:00
|
|
|
** Copyright (C) 2016 The Qt Company Ltd.
|
|
|
|
|
** Contact: https://www.qt.io/licensing/
|
2010-05-07 15:16:31 +02:00
|
|
|
**
|
2012-10-02 09:12:39 +02:00
|
|
|
** This file is part of Qt Creator.
|
2010-05-07 15:16:31 +02:00
|
|
|
**
|
2012-10-02 09:12:39 +02:00
|
|
|
** Commercial License Usage
|
|
|
|
|
** Licensees holding valid commercial Qt licenses may use this file in
|
|
|
|
|
** accordance with the commercial license agreement provided with the
|
|
|
|
|
** Software or, alternatively, in accordance with the terms contained in
|
2016-01-15 14:57:40 +01:00
|
|
|
** a written agreement between you and The Qt Company. For licensing terms
|
|
|
|
|
** and conditions see https://www.qt.io/terms-conditions. For further
|
|
|
|
|
** information use the contact form at https://www.qt.io/contact-us.
|
2010-05-07 15:16:31 +02:00
|
|
|
**
|
2016-01-15 14:57:40 +01:00
|
|
|
** GNU General Public License Usage
|
|
|
|
|
** Alternatively, this file may be used under the terms of the GNU
|
|
|
|
|
** General Public License version 3 as published by the Free Software
|
|
|
|
|
** Foundation with exceptions as appearing in the file LICENSE.GPL3-EXCEPT
|
|
|
|
|
** included in the packaging of this file. Please review the following
|
|
|
|
|
** information to ensure the GNU General Public License requirements will
|
|
|
|
|
** be met: https://www.gnu.org/licenses/gpl-3.0.html.
|
2010-12-17 16:01:08 +01:00
|
|
|
**
|
2012-10-02 09:12:39 +02:00
|
|
|
****************************************************************************/
|
2010-05-07 15:16:31 +02:00
|
|
|
|
2016-03-18 07:55:01 +01:00
|
|
|
#pragma once
|
2010-05-07 15:16:31 +02:00
|
|
|
|
2012-02-15 10:42:41 +01:00
|
|
|
#include <QMetaType>
|
|
|
|
|
#include <QString>
|
2010-05-07 15:16:31 +02:00
|
|
|
|
|
|
|
|
namespace Debugger {
|
|
|
|
|
namespace Internal {
|
|
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
class GdbMi;
|
2010-11-18 16:50:44 +01:00
|
|
|
|
2010-05-07 15:16:31 +02:00
|
|
|
//////////////////////////////////////////////////////////////////
|
|
|
|
|
//
|
|
|
|
|
// BreakpointData
|
|
|
|
|
//
|
|
|
|
|
//////////////////////////////////////////////////////////////////
|
|
|
|
|
|
2011-02-04 15:08:31 +01:00
|
|
|
//! \enum Debugger::Internal::BreakpointType
|
2013-04-09 10:59:36 +02:00
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
// Note: Keep synchronized with similar definitions in dumper.py
|
2010-10-28 12:18:38 +02:00
|
|
|
enum BreakpointType
|
|
|
|
|
{
|
2013-04-09 10:59:36 +02:00
|
|
|
UnknownBreakpointType,
|
2010-10-28 12:18:38 +02:00
|
|
|
BreakpointByFileAndLine,
|
|
|
|
|
BreakpointByFunction,
|
|
|
|
|
BreakpointByAddress,
|
2010-11-16 10:23:20 +01:00
|
|
|
BreakpointAtThrow,
|
|
|
|
|
BreakpointAtCatch,
|
|
|
|
|
BreakpointAtMain,
|
2011-03-04 19:26:11 +01:00
|
|
|
BreakpointAtFork,
|
|
|
|
|
BreakpointAtExec,
|
|
|
|
|
BreakpointAtSysCall,
|
2011-05-09 08:35:58 +02:00
|
|
|
WatchpointAtAddress,
|
2011-09-13 12:47:46 +02:00
|
|
|
WatchpointAtExpression,
|
2012-04-16 12:00:23 +02:00
|
|
|
BreakpointOnQmlSignalEmit,
|
2013-04-09 10:59:36 +02:00
|
|
|
BreakpointAtJavaScriptThrow,
|
|
|
|
|
LastBreakpointType
|
2010-10-28 12:18:38 +02:00
|
|
|
};
|
|
|
|
|
|
2011-02-04 15:08:31 +01:00
|
|
|
//! \enum Debugger::Internal::BreakpointState
|
2010-11-08 18:00:57 +01:00
|
|
|
enum BreakpointState
|
|
|
|
|
{
|
|
|
|
|
BreakpointNew,
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
BreakpointInsertionRequested, //!< Inferior was told about bp, not ack'ed.
|
|
|
|
|
BreakpointInsertionProceeding,
|
2010-11-10 16:33:11 +01:00
|
|
|
BreakpointInserted,
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
BreakpointUpdateRequested,
|
|
|
|
|
BreakpointUpdateProceeding,
|
2010-11-10 16:33:11 +01:00
|
|
|
BreakpointRemoveRequested,
|
|
|
|
|
BreakpointRemoveProceeding,
|
2010-12-16 12:05:48 +01:00
|
|
|
BreakpointDead
|
2010-11-08 18:00:57 +01:00
|
|
|
};
|
|
|
|
|
|
2011-02-17 13:00:11 +01:00
|
|
|
//! \enum Debugger::Internal::BreakpointPathUsage
|
|
|
|
|
enum BreakpointPathUsage
|
|
|
|
|
{
|
|
|
|
|
BreakpointPathUsageEngineDefault, //!< Default value that suits the engine.
|
|
|
|
|
BreakpointUseFullPath, //!< Use full path to avoid ambiguities. Slow with gdb.
|
|
|
|
|
BreakpointUseShortPath //!< Use filename only, in case source files are relocated.
|
|
|
|
|
};
|
|
|
|
|
|
2016-06-03 12:04:14 +02:00
|
|
|
enum BreakpointColumns
|
|
|
|
|
{
|
|
|
|
|
BreakpointNumberColumn,
|
|
|
|
|
BreakpointFunctionColumn,
|
|
|
|
|
BreakpointFileColumn,
|
|
|
|
|
BreakpointLineColumn,
|
|
|
|
|
BreakpointAddressColumn,
|
|
|
|
|
BreakpointConditionColumn,
|
|
|
|
|
BreakpointIgnoreColumn,
|
|
|
|
|
BreakpointThreadsColumn
|
|
|
|
|
};
|
|
|
|
|
|
2011-03-29 12:55:36 +02:00
|
|
|
enum BreakpointParts
|
|
|
|
|
{
|
2015-07-15 13:00:50 +02:00
|
|
|
NoParts = 0,
|
|
|
|
|
FileAndLinePart = (1 << 0),
|
|
|
|
|
FunctionPart = (1 << 1),
|
|
|
|
|
AddressPart = (1 << 2),
|
|
|
|
|
ExpressionPart = (1 << 3),
|
|
|
|
|
ConditionPart = (1 << 4),
|
|
|
|
|
IgnoreCountPart = (1 << 5),
|
|
|
|
|
ThreadSpecPart = (1 << 6),
|
|
|
|
|
ModulePart = (1 << 7),
|
|
|
|
|
TracePointPart = (1 << 8),
|
|
|
|
|
|
|
|
|
|
EnabledPart = (1 << 9),
|
|
|
|
|
TypePart = (1 << 10),
|
|
|
|
|
PathUsagePart = (1 << 11),
|
|
|
|
|
CommandPart = (1 << 12),
|
|
|
|
|
MessagePart = (1 << 13),
|
|
|
|
|
OneShotPart = (1 << 14),
|
2012-08-21 14:16:07 +02:00
|
|
|
|
|
|
|
|
AllConditionParts = ConditionPart|IgnoreCountPart|ThreadSpecPart
|
|
|
|
|
|OneShotPart,
|
2011-03-29 12:55:36 +02:00
|
|
|
|
2011-05-09 08:35:58 +02:00
|
|
|
AllParts = FileAndLinePart|FunctionPart
|
|
|
|
|
|ExpressionPart|AddressPart|ConditionPart
|
2011-03-29 12:55:36 +02:00
|
|
|
|IgnoreCountPart|ThreadSpecPart|ModulePart|TracePointPart
|
2011-06-27 10:37:57 +02:00
|
|
|
|EnabledPart|TypePart|PathUsagePart|CommandPart|MessagePart
|
2012-08-21 14:16:07 +02:00
|
|
|
|OneShotPart
|
2011-03-29 12:55:36 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
inline void operator|=(BreakpointParts &p, BreakpointParts r)
|
|
|
|
|
{
|
|
|
|
|
p = BreakpointParts(int(p) | int(r));
|
|
|
|
|
}
|
|
|
|
|
|
2010-11-15 19:05:31 +01:00
|
|
|
class BreakpointParameters
|
|
|
|
|
{
|
2010-11-15 17:04:29 +01:00
|
|
|
public:
|
2013-04-09 10:59:36 +02:00
|
|
|
explicit BreakpointParameters(BreakpointType = UnknownBreakpointType);
|
2011-03-29 12:55:36 +02:00
|
|
|
BreakpointParts differencesTo(const BreakpointParameters &rhs) const;
|
2011-10-20 10:45:59 +02:00
|
|
|
bool isValid() const;
|
2010-11-15 17:04:29 +01:00
|
|
|
bool equals(const BreakpointParameters &rhs) const;
|
2016-06-07 17:04:53 +02:00
|
|
|
bool conditionsMatch(const QString &other) const;
|
2011-05-09 08:35:58 +02:00
|
|
|
bool isWatchpoint() const
|
|
|
|
|
{ return type == WatchpointAtAddress || type == WatchpointAtExpression; }
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
bool isLocatedAt(const QString &fileName, int lineNumber, const QString &markerFileName) const;
|
2010-12-16 13:02:59 +01:00
|
|
|
// Enough for now.
|
2011-05-09 08:35:58 +02:00
|
|
|
bool isBreakpoint() const { return !isWatchpoint() && !isTracepoint(); }
|
2010-12-16 13:02:59 +01:00
|
|
|
bool isTracepoint() const { return tracepoint; }
|
2012-01-24 16:41:30 +01:00
|
|
|
bool isCppBreakpoint() const;
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
bool isQmlFileAndLineBreakpoint() const;
|
2010-11-16 11:48:17 +01:00
|
|
|
QString toString() const;
|
2016-06-07 17:04:53 +02:00
|
|
|
void updateLocation(const QString &location); // file.cpp:42
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
void updateFromGdbOutput(const GdbMi &bkpt);
|
2010-11-16 11:48:17 +01:00
|
|
|
|
|
|
|
|
bool operator==(const BreakpointParameters &p) const { return equals(p); }
|
|
|
|
|
bool operator!=(const BreakpointParameters &p) const { return !equals(p); }
|
2010-11-15 17:04:29 +01:00
|
|
|
|
2011-02-04 15:08:31 +01:00
|
|
|
BreakpointType type; //!< Type of breakpoint.
|
|
|
|
|
bool enabled; //!< Should we talk to the debugger engine?
|
2011-02-17 13:00:11 +01:00
|
|
|
BreakpointPathUsage pathUsage; //!< Should we use the full path when setting the bp?
|
2011-02-04 15:08:31 +01:00
|
|
|
QString fileName; //!< Short name of source file.
|
2016-06-07 17:04:53 +02:00
|
|
|
QString condition; //!< Condition associated with breakpoint.
|
2011-02-04 15:08:31 +01:00
|
|
|
int ignoreCount; //!< Ignore count associated with breakpoint.
|
|
|
|
|
int lineNumber; //!< Line in source file.
|
2011-05-16 12:37:04 +02:00
|
|
|
quint64 address; //!< Address for address based data breakpoints.
|
|
|
|
|
QString expression; //!< Expression for expression based data breakpoints.
|
|
|
|
|
uint size; //!< Size of watched area for data breakpoints.
|
2011-03-01 19:16:24 +01:00
|
|
|
uint bitpos; //!< Location of watched bitfield within watched area.
|
|
|
|
|
uint bitsize; //!< Size of watched bitfield within watched area.
|
2011-02-04 15:08:31 +01:00
|
|
|
int threadSpec; //!< Thread specification.
|
2010-11-15 17:04:29 +01:00
|
|
|
QString functionName;
|
2011-02-04 15:08:31 +01:00
|
|
|
QString module; //!< module for file name
|
|
|
|
|
QString command; //!< command to execute
|
2011-06-27 10:37:57 +02:00
|
|
|
QString message; //!< message
|
2010-12-16 13:02:59 +01:00
|
|
|
bool tracepoint;
|
2012-08-21 14:16:07 +02:00
|
|
|
bool oneShot; //!< Should this breakpoint trigger only once?
|
2010-11-16 10:23:20 +01:00
|
|
|
|
Debugger: Make most views per-engine instead of singletons
This is a step towards properly supporting multiple debugger
sessions side-by-side.
The combined C++-and-QML engine has been removed, instead a
combined setup creates now two individual engines, under a single
DebuggerRunTool but mostly independent with no combined state
machine. This requires a few more clicks in some cases, but
makes it easier to direct e.g. interrupt requests to the
interesting engine.
Care has been taken to not change the UX of the single debugger
session use case if possible. The fat debug button operates
as-before in that case, i.e. switches to Interrupt if the
single active runconfiguration runs in the debugger etc.
Most views are made per-engine, running an engine creates
a new Perspective, which is destroyed when the run control dies.
The snapshot view remains global and becomes primary source
of information on a "current engine" that receives all menu
and otherwise global input.
There is a new global "Breakpoint Preset" view containing
all "static" breakpoint data. When an engine starts up it
"claims" breakpoint it believes it can handle, but operates
on a copy of the static data. The markers of the static
version are suppressed as long as an engine controls a
breakpoint (that inclusive all resolved locations), but are
re-instatet once the engine quits.
The old Breakpoint class that already contained this split
per-instance was split into a new Breakpoint and a
GlobalBreakpoint class, with a per-engine model for Breakpoints,
and a singleton model containing GlobalBreakpoints.
There is a new CppDebuggerEngine intermediate level serving as
base for C++ (or, rather, "compiled") binary debugging, i.e.
{Gdb,Lldb,Cdb}Engine, taking over bits of the current DebuggerEngine
base that are not applicable to non-binary debuggers.
Change-Id: I9994f4c188379b4aee0c4f379edd4759fbb0bd43
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
2018-07-31 12:30:48 +02:00
|
|
|
bool pending = true; //!< Breakpoint not fully resolved.
|
|
|
|
|
int hitCount = 0; //!< Number of times this has been hit.
|
2010-05-07 15:16:31 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
} // namespace Internal
|
|
|
|
|
} // namespace Debugger
|